ODBC Data Source Name (DSN) Missing

[makingtrails]

Attempting to connect to my MySQL database via ODBC but unforunately the DSN is missing so I can't connect (Filemaker 13 Pro)

 

I've searched the forums for the solution and have come across a simular issue regarding 64 bit drivers but I am running a 32 bit O/S (Windows 7) therefore can only install 32 bit drivers.

 

Looking at this post http://forums.filemaker.com/posts/4c08106b66

 

"To setup DSN for 32-bit application you must use: %WINDIR%SysWOW64odbcad32.exe" however I do not have a SysWOW64 directory.

 

The ODBC connection has been tested and works ok so I am convinced it's FM related.

 

This is the driver I am using - http://dev.mysql.com/downloads/connector/odbc/

 

Any ideas?

 

Thanks

[Wim Decorte]

Since you are running 32-bit Windows, you only have one place to create DSNs, so that's easy.

 

You say that the DSN has been tested and works: was it created in the System DSNs tab of the ODBC control panel?

Follow-up: is this for ESS or for the Import from SQL Source / Execute SQL script steps?

 

If ESS: is the file hosted on FMS?

[milanm]

- You could read my article on this, many people told me it helped them resolve the similar problem: http://www.milanm.com/?p=491

- As the article is a bit out of date (made for FileMaker 11 and Windows server) i would also strongly suggest reading the FileMaker 13 documentation to find the exact matching driver: https://fmhelp.filem..._jdbc_guide.pdf

- Than you could read a thread where i posted the issue with ODBC driver and got very good replies from Wim Decorte and Josh Ormond, regarding ODBC driver with FileMaker 13 Server hosted on Windows: http://fmforums.com/forum/topic/92476-filemaker-13-does-not-see-the-odbc-driver/

 

These should get you there somehow, usually if you can not see the DNS means either that it is not properly configured and connected to the MySQL data source you need to reach, OR that it is the wrong driver for the version of FileMaker you are using.

[makingtrails]

Thanks for your replies. I resolved this issue by reinstalling the ODBC driver and restarting my computer. Tested and now works great. Thanks for your help