Updating MySQL ODBC Driver - problems with MS Access

[rafael]

I recently installed MySQL ODBC 5.1 Driver, but my MS Access files are still trying to use version 3.51, giving a generic error - somethings like ODBC – connection to ‘{MySQL ODBC 3.51 Driver} failed.

The only way I can fix them is to re-link the tables back in MS Access which is very time consuming.

Is there a quick fix to getting all MS Access databases to use the latest driver? Hope you can help.

 

[HiTechCoach]

My experience has been that you will have to delete all the table links and relink all the tables.

I have a custom built Link Table manage where I store the name of each table all the back end. This way I can use code to relink the tables.

This may help:
Relink ODBC tables from code

 

[rafael]

My experience has been thta you will have to delete all the table links and relink all the tables.

I have a custom built Link Table manage where I store the name of each table all the back end. This way I can use code to relink the tables.

This may help:
Relink ODBC tables from code

Thanks, do you think its possible using that code to re-link the tables and specify a particular MySQL ODBC driver?

 

[boblarson]

Why not just use the Linked Table Manager to relink?

 

[Banana]

Seems to me that the code looks at DSN in registry. If we're going to do it in code, I'd probably just do it without DSN and save myself all the trouble. Google for Doug J. Steele's DSN-less connection, which you just need to change the connection string and thus refer to newer driver and you'd be done.

 

[HiTechCoach]

When developing, I will use an ODBC connection. For some databases, when ready to deploy, I use Doug J. Steele's code to change it to a DSN-less connection before I deploy the new MDE

As Banana suggested, here is the link:
Using DSN-Less Connections

 

[rafael]

Thanks again for this guys (I added to your reputations some time ago), especially for the link, its been really helpful to me. I've been using the script to convert my access backends to connect to MySQL and its working great.

I was wondering, is it possible to have the DSN-less script in an external mdb project, then include an extra parameter to specify the location of the access database to connect to and make DSN-less?

If there was, then I wouldn't need to duplicate this code on all my access projects. I think its possible but any help would be greatly appreciated.