We created an importer database in filemaker 4 for PC, in the Dutch language using European number conventions. (4.000,00 = 4,000.00). When data is imported from a simple comma delimmited data file, the numbers read (for instance) 41,99 for 41.99. However, when the data was exported to another file and used in calculations, the comma was not treated as a decimal and the number became (in value) 4,199 (as opposed to $41.99). We then converted the files to my Mac, converting to US number conventions and the same thing is occuring. We played around with all the system formats, etc.

Has anyone heard of such a problem and any suggestions on how to fix it???

Thanks

The term "comma delimited" should be the clue here. The comma normally indicates that one field ends and the next begins. In data that has embedded commas, the exporting software will often enclose the data in quotes to keep the data in one piece. It looks like one of the applications is not quoting the data when it exports, and quite possibly the intermediate application just doesn't recognize a comma as a valid decimal separator.

If possible use tab delimited text files for import and export. They are a lot safer.

[This message has been edited by BobWeaver (edited January 09, 2001).]