Exporting as ".15"; when imported shows up as ".149999999"

[geraldh]

Hello,

I am exporting some LedgerLines to an excel document and then importing them into a table called InvoiceLines. A field for an extra charge does not seem to import properly. If the field has a value of ".15" it is imported as ".14999999". When the value of ".20" is inputed it is exporting/importing properly.

I've worked around this by making it display as a percentage, and then restricting it to 2 decimal points.

It displays properly, but my calculations are off (very slightly, but still inaccurate).

I'd like to correct the root of this problem, but can't seem to figure it out.

Can any one give me some suggestions.

Thank you

[doughemi]

The root problem is that floating point numbers get slightly off during the translation processes. As a workaround, try setting up the ExtraCharge field with an autoentered calculation Round(self; 2) . Uncheck the "Do not replace existing value" checkbox.

[comment]

See also:

http://help.filemaker.com/app/answers/detail/a_id/9281

In general, Excel is probably the worst choice for an intermediate format.

[Lee Smith]

Have you tried exporting the data using the current layout formatted as you want? See number 11 here link in the help for Exporting data from FileMaker Pro

[geraldh]

thank you all for your help.

I am still a novice, and therefore I simply thought of excel as the default intermediate format.

I will experiment with the other formats. Also this will help stretch my Filemaker development skills!

[comment]

I am exporting some LedgerLines to an excel document and then importing them

In which application is LedgerLines? If it's Filemaker, why not import directly from the source?

[geraldh]

In which application is LedgerLines? If it's Filemaker, why not import directly from the source?

I'm exporting from LedgerLines table to EstimateLines table within the same Filemaker file.

I don't know if this is conventional...?

Still a novice, please correct me if I'm not following best practices.

[comment]

You can import directly from another table in the same file. Whether that's a good idea depends on the purpose: as a rule, it's best to store data in one place only - but there are exceptions.

[geraldh]

The LedgerLines is actually a temporary worksheet/table that evolves and is used to generate Estimate(s), Profit & Loss Statements, and Invoices, and assist in other tables.

The contents of a Ledger (and its LedgerLines) evolves as the Client and our company firm firm up details (and change our minds) about an Event.

I shall look into importing directly -- sounds like a good idea!