64 bit driver for DSN for MS access database

Anonymous
2010-01-21T16:03:27+00:00

I have windows 7 professional 64 version on my laptop.  I tried locating DSN (data source name) for MS access data. 

It is giving me an option for only SQL server database.

Defining connectivity to MS access database through DSN is very critical to my ASP applications working through IIS (internet information services)  After reviewing the solutions on the web I concluded currently there is no 64 bit driver.

Should I downgrade my windows 7 professional to 32 version

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-01-22T17:42:45+00:00

Hi smantha11,

Currently Microsoft does not have any 64 bit ODBC drivers available for the Office products.

However, as long as the application that you want to connect to is 32 bit, you can use the 32 bit ODBC drivers to create the DSN. To get to the 32 bit ODBC drivers, the 32 bit Data Source administrator must be used. The 32 bit Data Source administrator must be launched directly if you are using a 64 bit OS. The file should be located at the following path:

c:\windows\sysWOW64\odbcad32.exe

Hope this helps!

Kathy

Was this answer helpful?

60+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
ScottGem 68,840 Reputation points Volunteer Moderator
2010-01-22T22:50:50+00:00

You can download the drivers here:

http://www.microsoft.com/downloads/details.aspx?familyid=7554F536-8C28-4598-9B72-EF94E038C891&displaylang=e

This file will add Access to the list of file types in the ODBC administrator.

Not sure if its 32 or 64 bit. But it worked on a machine running 64bit Win 7


Hope this helps, Scott<> P.S. Please post a response to let us know whether our answer helped or not. Microsoft Access MVP 2009 Author: Microsoft Office Access 2007 VBA Technical Editor for: Special Edition Using Microsoft Access 2007 and Access 2007 Forms, Reports and Queries

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

50 additional answers

Sort by: Newest
  1. Anonymous
    2013-05-27T11:32:44+00:00

    thanks it's work good

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-05-09T17:13:49+00:00

    Kathy,

    I am hoping you may be able to help me.

    I am caught in the 64/32 bit Access trap.  I have 32 bit office 2010 installed and the only Access drivers that would install are the 32 bit ones.  However, I am writing a custom application that is 64 bit and I can't seem to get it to work with the 32 bit drivers by default.  It keeps looking for 64 bit drivers and failing with an error message.  When I use the "Microsoft MS Access" name in code it keeps looking for the 64 bit version even though I have the 32 bit drivers installed.  I had to manually create a user DSN and give it a different name an then refer to that name to connect.  The problem is that this app is going to be distributed throughout the company and I have to be able to hit the default "Microsoft MS Access" name.

    Hope you understand what I am talking about and can offer a solution.

    Mike

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-05-05T23:04:12+00:00

    If you are receiving this error, then it means you have a 64-bit component somewhere in your application stack. I recently got this error when trying to connect to an Access Database from a Java application on Win 7 X64. The fix for me was to uninstall all 64 bit versions of of the Java JREs that I had on my system. Even though I had specified a 32-bit JRE and disabled the 64 bit JREs through the Java console and specified a 32 bit version for my PATH environment variable, it was still defaulting to a 64-bit Hotspot Java Virtual Machine. I don't if that is a JRE bug, or if I was missing a configuration somewhere. Verify the following commands from the command line:

    java -version

    javac -version

    echo %PATH%

    echo %CLASSPATH%

    My guess is that if you run java -version, you will not get the following:

    Java HotSpot(TM) Client VM (build 20.45-b01, mixed mode, sharing)

    You will instead get something similar but that says 64 bit rather than mixed mode. That is probably your issue.

    Also verify your ODBC settings are configured correctly

    If you're trying to run this from an IDE such as Eclipse, you will also need to verify settings specific to your IDE.

    This is not a Microsoft issue. I can confirm the 32 bit driver works for connecting from 32 bit Java applications on Windows 7 x64, Win XP x64, and Server 2012.

    Was this answer helpful?

    0 comments No comments