Issue with the ODBC driver being used to talk to MySQL? Maybe MySQL was updated to a new version and you need to update/change the ODBC stuff as well?
I have checked and the ODBC driver on the server is up-to-date for the version of MySQL. The indexes on the MySQL tables have been rebuilt.
The issue is ongoing. I seem to have one MySQL table that will consistently fail but it is not the only point of failure, just the one that I can consistently get to fail doing nothing particularly onerous. The failing table only has 150 records and I am connecting to it from a local global table. I have checked to make sure that my field types match the MySQL field types for the joins.
I cannot migrate this solution and all the lovely FM 13 features that I have built using popovers and slide panels.
Anyone else have problems with clients closing unexpectedly on Macs?
In the end you were right about it being a driver issue. Here is what seemed to be the problem.
When I set-up my MySQL ODBC driver on my new FM 13 server machine, I installed a 32-bit version of the current MySQL ODBC driver. Because of the way our servers are set up, that probably seemed like the appropriate choice and, well, frankly one might think that the 32-bit drivers are appropriate for something named "system32", right?. And that worked fine except for when I was using a Mac FM 13 client trying to access the MySQL data delivered to me by the FM 13 Server using the 32-bit driver.
I went around the block a few times before I realized that indeed system32 is where you put 64-bit drivers and SysWOW64 is where you put 32-bit drivers. Go figure! I'm sure that there is some deep logic to that but it wasn't until I had reinstalled my FM server, and installed a 64-bit MySQL driver into the SysWOW64 directory that I realized that I had the paths backwards.
So here are some takeaways from my Windows 8 server environment:
- Drivers will install using /system32/odbcad32.exe by default regardless of whether they are 32-bit or 64-bit.
- It is possible to install drivers of either type using the SysWOW64/odbcad32.exe path, but it is not clear to me how you make FM clients recognize drivers that are installed using that path. Fortunately, I don't think I need to know this now that I have the drivers I need in the correct place.
- Just don't get caught off guard like I did by the odd logic of the exe paths!