1 of 1 people found this helpful
FileMaker Pro (and FileMaker Server scheduled scripts) requires a 32-bit DSN. If you have a 64-bit version of Windows, you must use a 64-bit DSN and ODBC driver for FileMaker Server 12 ESS data sources.
Thanks, Greg. So if I need to do imports via Pro or scheduled scripts, and I have ESS connections, I need both 32-bit and 64-bit drivers?
This is what I'm getting from my Oracle guy:
"Yes, but only one Oracle Home can be default. You will need to somehow control what you are getting from which Oracle Home. If not, you will most likely cross-link the Homes, which usually does not function very well.
"The 32 bit client should work with a 64 bit app."
I'm certain your Oracle guy knows more about Oracle than I do.
My experience with FileMaker 12 has been that in order to use ESS with the server's DSN with files hosted by FileMaker Server 12 on a 64-bit version of Windows, a 64-bit DSN and ODBC driver must be used. Fmserver.exe is a 64-bit process and it won't work with a 32-bit DSN. Scheduled scripts are run by fmsase.exe, which is still a 32-bit process. It won't work with a 64-bit DSN. FileMaker Pro.exe is a 32-bit process. It will only work with a 32-bit DSN.
I haven't experienced any problems with having both 32-bit and 64-bit DSNs on a server, but I am certainly not an Oracle expert. If it is a problem in your environment, you could consider installing FileMaker Server on a 32-bit version of Windows or you could choose not to run ODBC imports via FileMaker Pro or scheduled scripts on the server. You could always do the import with FileMaker Pro on a different workstation with its own 32-bit DSN.
Thanks, Greg. Still pursuing ...