Hi,
I have a MySQL table on a MacOSX 10.4 server and Filemaker Pro Server 7. I am using the "Actual Technologies" ODBC driver for this project. I have a number of fields I am trying to import from MySQL into a client FM DB.
The Problem:
Two of the MySQL fields are formatted as DATETIME and they serve as a creation and update AUTO-ENTER fields using the NOW() MySQL function. The fields are auto filled with a string that looks like this 20060125132456 (yr, m, d, hr, sec) ....when using the FM ODBC importer these two fields import and look like this 365: 12: 23 .....all other import fields work perfectly..I have tried changing around FM field types...nothing seems to work ...I would like it if the fields were imported either as a text string (just like MySQL) or with FM DateTime formatting...
Is there an EZ solution?
Is there a workaround?
Is there a product I can buy (ODBC) that will greatly simplify communication back/forth between FM and MySQL and will resolve these field type differences automatically?
Thanks,
Jim E
I have a MySQL table on a MacOSX 10.4 server and Filemaker Pro Server 7. I am using the "Actual Technologies" ODBC driver for this project. I have a number of fields I am trying to import from MySQL into a client FM DB.
The Problem:
Two of the MySQL fields are formatted as DATETIME and they serve as a creation and update AUTO-ENTER fields using the NOW() MySQL function. The fields are auto filled with a string that looks like this 20060125132456 (yr, m, d, hr, sec) ....when using the FM ODBC importer these two fields import and look like this 365: 12: 23 .....all other import fields work perfectly..I have tried changing around FM field types...nothing seems to work ...I would like it if the fields were imported either as a text string (just like MySQL) or with FM DateTime formatting...
Is there an EZ solution?
Is there a workaround?
Is there a product I can buy (ODBC) that will greatly simplify communication back/forth between FM and MySQL and will resolve these field type differences automatically?
Thanks,
Jim E