I have FM11A(the client is only now, but the project should be launched on the FM server 11 or 12-13) on the WinXP machine, where I also run MySQL server (5.5)for testing purposes.
I have a database fully working on filemaker, and I am developing a database with MySQL databases to work on the Internet.
My goal is to be able to perform bi-directional synchronization between Fm and MySQL, leaving 2 databases as completely independent objects (so I would avoid writing FM directly in MySQL tables, that is, have FM as front-end and MySQL as backend).
I managed to import the MySQL table (demographics) into the FM database (where there is another “demographics” table), 2 tables have exactly the same fields, and importing from MySQL-Demogrto FM-Demogrusing ODBC \ ESS works very well.
When I open FM and import records from MySQL using the shadow table, everything goes smoothly and I can see the new records on the original FM table as I wanted.
Note that I can also write data directly to the MySQL-Demogr table using FM and writing to the shadow table.
The problem occurs when I try to export FM data to MySQL: it is obvious that the ODBC \ ESS system works very well in one direction (import FM from * SQL), but not the other (FM export in * SQL) I'm still trying to determine the most efficient (i.e. simple \ fast and scalable) way to export records originally inserted in FM to MySQL.
The old way is a script to export to a .csv file from FM, and then load the new data into MySQL, possibly using a temporary table inside MySQL. This should be very fast and absolutely doable, although I would prefer to use ODBC \ ESS, if at all possible.
The easiest way is to export directly from FM to MySQL using the shadow table, but it does not work:
. FM ODBC (MySQL), -, ( ?)
. MySQL (MySQL-Demogr) FM ( FM-Demogr → MySQL-Demogr), , MySQL, MySQL, .
- filemaker SQL- MySQL-Demogr ODBC... , , , 2003-2009 , -, . , ExecuteSQL script mopsr ? - ( $100), ,
, (Excel SQLYog) SQL (FM MySQL) script . , FM-MySQL, .
.