I’ve been connecting a Filemaker Pro solution with a WordPress website for a client. In a matching relationship to a Gravity Forms table (rg_lead_detail) I was matching a local field with the Gravity Forms column “field_number” which is defined as a float. I noticed that the relationship was only matching whole integers, not numbers with decimals like “1.3”.
Researching this problem led me to this article about MySQL float columns not being precisely recorded:
If you store the number 1.3 in a float column of your database table, MySQL actually stores the number 1.2999999523162842.
My quick solution was to create two calculation fields, one high and one low based on the local field. The high calculation added 0.05 to the field, and the low field subtracted 0.05. This assumes the field only goes to tenths.
It works for this application, but I don’t see it working for solutions needing precision and accuracy to multiple decimal places.
One thought on “Filemaker and MySQL Floats in Relationship”
I’m fairly certain this is a consequence of using the free MySQL Connector/ODBC database driver. Using a commercial database driver, like Actual Technologies’ ODBC Driver for Open Source Databases, seems to alleviate the issue. (http://www.actualtech.com/product_opensourcedatabases.php)