MS-Access 2007/2010/2013 ODBC 32-bit connector to MySQL 64-bit Server on W-7 localhost?

EE Experts,

I have a MS Access report application that connects to a MySQL database using ODBC with SELECT privileges only. On my Windows XP machines this has never been a problem. It was 32 bit all the way. 32-bit versus 64-bit was never an issue. But making it work from MS-Access 2007/2010/2013 using a 32 bit connector to a 64-bit server has become a problem. I had this working at one time in MS-Access 2007. Now that doesn't work either. I must of messed something up and don't know what it is. I have attached 5 JPG screen shots to show what I am getting. I hope somebody has a solution for this problem.

Thanks,
Ted Palmer
ODBC--connection-to.jpg
ODBCdataSourceAdministrator-01.jpg
ODBCdataSourceNameDeclared.jpg
ConnectionSuccessful-01.jpg
Users-Privileges.jpg
Ted PalmerInformation Technology ConsultantAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Kelvin SparksConnect With a Mentor Commented:
Note there is a size difference between to two odbcad32.exe files - these are the same as the two on my 64 bit system. As I mentioned, Access can only use the 32 bit version which is located in the SYSWOW64 folder. I have spent many hours on this as a customer of mine ships an Access runtime to around 100 customers worldwide and we have had to resolve the setup in many different environments. If you manually create an ODBC connection, you have to use this ODBC panel. If you do it from Access it self, it will put it in this one - not the Systrem32 one.

Kelvin
0
 
Ted PalmerInformation Technology ConsultantAuthor Commented:
This may not be a 32-bit versus 64-bit issue. I just know it doesn't work like I expect it to. I can define the Data Source Name (DSN) correctly, and it tests OK on the connector declaration screen. But it doesn't work when I try to run it. Oh! also in linked table manager the DSN doesn't appear.

Ted Palmer
0
 
Kelvin SparksCommented:
For Access 32 bit) you MUST use the 32 bit ODBC driver. If you use the 64 bit one, you will not be able to see it in the linked table manager.

In 64 windows, the ODBc connections you see by default from Control Panel are the 64 bit ones. To view the 32 bit ones you need to go to C:\Windows\SYSWOW64 and look for odbcad32.exe. This runs the 32bit ODBC control panel.

If you are downloading drivers - always use the 321 bit ones - even if connecting to a 64 bit server.

Kelvin
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
Ted PalmerInformation Technology ConsultantAuthor Commented:
Kelvin,

First of all thank you for your help. It is desperately needed, and much appreciated. First of all I am challenged in responding to your comment because I am getting so many conflicting results. Please see attached JPG file of 4 screen shots. You can see that the property screen for both files are almost the same. The property screen for odbc32.exe from directory C:\Windows\SYSWOW64 is on the left. And the one on the right is from directory C:\Windows\system32. The one on the left should be for 32 bit connectors, and the one on the right should be for 64 bit connectors. They both display what looks like the same ODBC data source administrator that causes the same data source parameters screen to be displayed. This is all from a PC for which my MS-Access 2007 Reports module works just fine. I am not disputing anything you are saying, but I am getting conflicting results. I have to go do the same thing on the remote client PC that is failing.

If you can shed any light on this while I am doing that, it would help.

Thank you for your time and effort.

Ted Palmer
odbcad32-Properties.jpg
0
 
Ted PalmerInformation Technology ConsultantAuthor Commented:
THANK YOU..!!
0
 
Kelvin SparksCommented:
A pleasure. I sweated many hours resolving this a few years back, so can understand the nightmare you were enduring.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.