64 bit Win7, cannot use ODBC


I just installed yesterday to Win7 and immediately wanted to compare an Access 2010 database to a sql database. I used the 32 bit ODBC data source tool to create a DSN. But I cannot use it in the SQLdiff connection editor. the test button goes red and the warning dialog says that the specified DSN contains an architecture mismatch between the driver and the application.
I can make an ODBC connection to a SQL server, but not Excel or Access files.
hoping to get some real world use out of this very soon,


msorens wrote Mar 3, 2011 at 9:10 PM

I wanted to get back to you promptly so I tried what I had readily at hand: 32-bit Win7 with an Excel 2003 file as a data source (I don't have Access installed). This combination works fine. So to isolate further, we need to determine if the issue is 64-bit vs. 32-bit or Office 2003 vs Office 2010. The ODBC Data Source Administrator specifically calls out "*.xls" for the Microsoft Excel Driver and .mdb for the Microsoft Access Driver, so I would have thought that .xlsx and .accdb files do not have ODBC support. But you said you defined an ODBC connection with the ODBC tool--how did you do that? Also, you might try degrading your files to .xls or .mdb and see if those will work on 64-bit Win7.

bdelaney wrote Mar 3, 2011 at 9:42 PM

Good ideas for further troubleshooting. I will also try in another Win7 environment.
I used the 32bit ODBC tool to get the Access DSN created.
Link at MS:

msorens wrote Mar 4, 2011 at 3:12 PM

I learned something useful as I investigated further on my end:
As I stated my Win7 ODBC Data Source Administrator showed only an Excel driver for .xls files. But when I checked on my XP box it also showed an Excel 2010 driver (xls,xlsx,xlsm,xlsb) and Access 2010 (mdb,accdb). I thought for a minute and then realized that because I installed Office 2010 on XP it likely made those drivers available, while my Win7 has no Office2010, so no drivers for it. Thus, I was able to try the combination of XP and Excel 2010 and can confirm that it works fine.

hypergreatthing wrote Jun 14, 2012 at 3:43 PM

Fairly sure this is a 64 bit application vs 32 bit driver issue.
Using the syswow64 (odbc manager for 32 bit drivers on a 64 bit os) won't work. Pretty sure the .net application was compiled using any processor type.
Solution is to install the access 64 bit driver.
If you have office 32 bit on a 64 bit os the windows installer won't work.
The work around is located here: