ESS sources use the drivers and DSNs installed on the server, not the client. If I had to guess, I'd say you probably need to get the server admin to install the appropriate drivers / DNSs on the server.
The Server is running on the same machine as FMP12.. Here is my setup:
- FMP12 and FMSA12 on a Windows 7 Pro machine
- DSNs setup and working on machine with FMP12 but not on FMSA12
- DSNs have authentication "embedded" inside of the FMP12 application and work when using the app through FMP12 as well as connecting to it via FMG on iPhone and iPad.
Maybe that will help clear this up.
1 of 1 people found this helpful
Although you didn't say it, I would guess that you are running the 32-bit version of FMSA on the 64-bit version of Windows 7, and that you have configured your ODBC DSN using the 64-bit ODBC Administrator.
If that's the case, then you need to remove the DSN using the 64-bit ODBC Admininstrator, then launch the 32-bit ODBC Administrator located at:
and configure your DSN with that.
BTW, ESS will prompt for database credentials on almost any failure to connect, regardless of the reason. That's true here, when the underlying problem is that it can't even load the ODBC driver.
Actual Technologies - ODBC for Mac OS X
Try installing the 64 bit driver. Server is a 64 bit app but pro is still 32 bit.
actualjon, you helped me get to the bottom of it. I am actually using FileMaker Server Advanced 64-bit instead of 32, so I just needed to add the same DSNs to the 64bit ODBC manager. Once I did that now Pro and Server are working correctly.
Thanks so much guys!