OBDC Drivers for access

[boblarson]

You may need to try re-installing the whole Office Suite. And, make sure you go into CUSTOM install and select EVERYTHING.

 

[gemma-the-husky]

i have loads of access drivers showing in my odbc panel

control panel/administrative taks/odbc - something like

drivers tab and connection pooling specifically refer to accdb, so they must have comer form 2007

 

[boblarson]

And mine (Win7 64bit) shows:

But I don't seem to have the driver installed either, so I'm wondering if it really does work on 64 bit.

 

[Banana]

Not to sound like a broken record, but are you sure this isn't the default 64-bit ODBC administrator. They have two different ODBC Administrator, and stores the 64-bit/32-bit drivers in separate locations, and if my memory serves, 64-bit ODBC administrator is used by default. Since there's no 64-bit drivers for Access, it won't work, so we need to manually select 32-bit ODBC (again, going by memory, it'd be named ODBC (x86) Administrator then we can use driver from there.

 

[boblarson]

Not to sound like a broken record, but are you sure this isn't the default 64-bit ODBC administrator. They have two different ODBC Administrator, and stores the 64-bit/32-bit drivers in separate locations, and if my memory serves, 64-bit ODBC administrator is used by default. Since there's no 64-bit drivers for Access, it won't work, so we need to manually select 32-bit ODBC (again, going by memory, it'd be named ODBC (x86) Administrator then we can use driver from there.

Actually, you are a bit reversed, it would appear. The DEFAULT one that is shown in Control Panel (for Win7) is actually the 32-bit ODBC panel. That sounds strange, but when I look at the path of the shortcut, it shows:

%windir%\system32\odbcad32.exe

as the Target and if I bring that up, it gives me those errors I posted in screenshot. However, if I go navigate to

C:\Windows\SysWOW64

and then open

odbcad32.exe

It actually brings up the WORKING one which does NOT give me errors.

So, even though the odbcad32 is the same file name for both, the one that is loaded appears to be the 32 bit one under the 32 bit folder and the one under the 64 bit system folder is really the one I need to substitute.

I would check to see if it is the same like that for Vista.

 

[Banana]

Thanks for the correction. I no longer have a 64-bit OS so I couldn't test (hence going by memory. Not exactly the best way to do things...), but I know I was quite annoyed when I found out that there were two locations and you had to be careful with which ODBC administrator you were looking at, though from the GUI standpoint, they appear identical.

 

[bohemian9485]

It's quite there are actually two locations for managing ODBC connections on a 64-bit machine. I installed Access 2K3 on a machine running Windows Server 2008 Standard 64-bit. I also installed Visual Basic.Net 2005 Express on the same machine. When I tried to connect to an Access database using VB.net it says the Access ODBC drivers were not installed?! That's when I discovered that there are two ODBC managers in the control panel, one for 64-bit and the other one for 32-bit. Although Access ODBC drivers are listed under the 64-bit ODBC manager, when I click the Configure button, it says the drivers were not installed correctly and needs to be re-installed. But when I clicked the Add button, all I see is drivers for SQL Server connection. In the 32-bit ODBC manager, the Access drivers are listed correctly. Just don't understand why Microsoft has to create this kind of *thing* to "confuse" their own applications?

 

[boblarson]

It's quite there are actually two locations for managing ODBC connections on a 64-bit machine. I installed Access 2K3 on a machine running Windows Server 2008 Standard 64-bit. I also installed Visual Basic.Net 2005 Express on the same machine. When I tried to connect to an Access database using VB.net it says the Access ODBC drivers were not installed?! That's when I discovered that there are two ODBC managers in the control panel, one for 64-bit and the other one for 32-bit. Although Access ODBC drivers are listed under the 64-bit ODBC manager, when I click the Configure button, it says the drivers were not installed correctly and needs to be re-installed. But when I clicked the Add button, all I see is drivers for SQL Server connection. In the 32-bit ODBC manager, the Access drivers are listed correctly. Just don't understand why Microsoft has to create this kind of *thing* to "confuse" their own applications?

Actually, as I mentioned to Banana, you have this backwards. The actual default that is there in the ODBC item when you go to the Admin Control Panel and open the Manage Data Connections (ODBC) is the 32 bit version which resides in the System32 directory. If you want the actual version which will work go find the odbcad32.exe in the 64 bit Windows directory and run it instead.