Hello,
the software I develop (with usage of Valentina) is able to open =
different volumes (not disk drives, but editions). Every volume has it's =
own database with different tables. An additional text file stores =
information about which fields of certain base objects should be used to =
display certain text within the software. This way the structure of =
every volume of the product can be different from the others, but the =
software can deal with it without being changed every time.
But there are certain fields that have to be in every base object. I =
check for these fields, and if they can't be found, the software alerts =
and stops.
Now a costumer says he has problems running the software on Japanese =
Windows. He gets exactly this alert message saying that there are some =
fields missing. But running the software on a German system the fields =
are found.
Here's how I check for the fields: When opening a volume, I store the =
field names (converted to symbols) and their position in a property =
list, e.g.=20
[#Dateiname: 1, #Seriennummer: 2, #Bildnummer: 3, #Sanguetti: 4, =
#Fumagelli: 5, #Kategorie: 6, #Serientitel: 7, #Jahrgang: 8, #Drucker: =
9, #format: 10, #Bildtitel: 11, #Beschreibung: 12, #CD__Nummer: 13, =
#Katalog__Nummer: 14, #Erkl_ae_rung: 15]
Then I check for the two fields that I need to be in every base object:
if thePropList[Katalog__Nummer] =3D void or thePropList[#CD__Nummer] =3D =
void then
alert "Fields missing."
halt
end if
As you see, the field names do not contain any special German characters =
(Umlauts), but only characters from A to Z and the underscore.
Can you imagine what's going wrong on the Japanese system? Would it be =
enough to change the country/language setting on that system?
Regards,
Christian Kirchhoff
©2002 Christian Kirchhoff |
