Yes, it's been a while since I posted. But I've not run into a problem like this in a while. Yes, FileMaker 13 is said to be looming on the horizon. But there's still no sign of the loom. Certainly no fruit of the loom, as it were.
Anyway, we decided it was high time to upgrade our FileMaker ecosystem from 10/11 to 12. Everything went fine until I tried to transfer data from our FM databases to our MySQL ones. (Necessary, since our website sits on the latter and needs the data from the FMP files.) And it didn't transfer.
Poking around, I came up with an error about "the DSN has an architecture mismatch" blah blah, as if the computer were upset that I'd mixed Gothic and Baroque. Anyway, for a few reasons I had only today to solve the problem, but the more I researched the deeper in failure I seemed to be mired. So I did what any man in my desperate position would do.
Cry? Almost. Pray? Certainly.
There were a number of points that obscured the solution, like the fact that you need FMS Advanced for ODBC connections that are incoming, but not for ones that are outgoing. I wasn't aware of that difference at first. And some versions of FileMaker require you to use 32-bit DSNs for ODBC even on 64-bit platforms, but such is not the case in FM 12, and I didn't find that documented anywhere. This last point was critical, because in the end the solution was...
...to recreate the 32-bit DSN we'd been using as an identical 64-bit DSN! Ta-dah!
Remember, nothing else on our systems had changed, only the version of FileMaker Pro/Server.
I'm glad that's over with. If a server is supposed to serve, then I feel like the server's server. Server of the server of God (which I guess would be Apple, since they own FileMaker--Apple-qua-God is an interesting thought).
Friday, October 4, 2013
Subscribe to:
Posts (Atom)