1 of 1 people found this helpful
Let me guess, your server is a 64bit OS, right?
If so realize FileMaker Server is a 32bit program, and as such the DSN (DataSourceName) must be setup in the 32bit ODBC manager not the 64bit ODBC manager(which is the default on 64bit OS).
The file is located in the system folder like so: C:\Windows\SysWOW64\odbcad32.exe
This is the link for windows 7, but server 2008 is also in a syswow64 directory.
Wow. I wish I had met you a long time ago. That is awesome. Just opened up a whole new would for us.
And, after you have the ODBC source corrected (per Tim), keep in mind that any Server-scheduled scripts might still not be able to read the ODBC data while running server-side instead of clinet-triggered.
For some reason, Servers can only read "server-local" data during script executions, though client machines can read multiple data servers just fine. I wish that would get fixed.
If the ODBC connection is working, test any server-scheduled script that uses the ODBC source before assuming it will run without error.
Glad to be of assistance. Maybe someday Filemaker will be fully 64bit software. Also be aware that ESS (External Sequel Source) by its nature goes both ways, so if you wish a read only connection, set it up on the SQL side. You can delete a whole table if you’re not careful. Kind of like a steak knife, very good at dinner time, but watch out for the fingers. Ouch.
I got to go, all this talk of dinner is making me hungry.
Timothy R Whisenant
Plastic Fusion Fabricators, Inc.