There has been a long documented issue with importing data from Excel into FileMaker that looks much the same as this. (A floating point value has extra, non-zero digits in the final few digits of the field's precision).
In that case, the difference is in how the two apps store floating point numbers. In both apps, the floating point numbers is stored in binary scientific notation. The "mantissa" portion has a different number of total digits (precision) in the two apps and this difference, when the values are displayed in base 10 in order to make sense to us humans, can create such small discrepancies.
I suspect that what you report is much the same issue.
Thank you for the answer!!
Is there any way to atleast display the data upto 2 decimals only in FileMaker?
In the inspector, you can set data formatting for the field object to a specific number of decimals. This will display a value rounded to that precision.
But when i click in the field, it again shows 8 decimals. I need to see only 2 decimals on clicking.
And that is exactly how this is intended to function. It changes the displayed value, not the stored value.
If this is data imported from the ODBC source, you can set up an auto-enter calculation using the round function to modify the actual value to permanently remove these non-zero digits from the value.