Unable to install ODBC drivers

Question

I am unable to install any ODBC driver in Vista. mySQL driver completes installation but the driver is not visible in the ODBC administrator panel. I tried installing the MDAC drivers but nothing happens. In fact, no drivers except "SQL Server" is visible which came along with the Vista installation. I am using the Vista public beta build 5384.  My apps use ODBC for data access from MS-Access and mySQL 5.0, so I need to test compatibility.

Can anyone help?

Answer 1

So whatever did happen to this one?

I've got the same problem - cannot install any ODBC drivers on Vista 64 with IIS7. All I have is the SQL Server driver and not even installing the AccessDatabaseEngine or the MDAC_TYP (2.8) will change things.

I need to get a website up that is using an Access 2003 .mdb file and I can't get the JET 4.0 engine installed. Tried importing the old .mdb into a new .accdb Acces 2007 file, changed my connection string, still no dice. What am I missing?

Please, anyone?

Answer 2

have u solved the problem??  i have the same situation...

Answer 3

If you using Jet on Vista 64 you need to user 32 bit, compile for x86 not any cpu. If your using native code, your out of luck because there is no 64 bit driver for Jet for Vista.

Answer 4

There are two copies of odbcad32.exe on Windows Vista x64, one is stored at c:\windows\system32\ and one is stored at c:\windows\syswow64\.  You need to run c:\windows\syswow64\odbcad32.exe to have access for all other ODBC drivers.

 

Answer 5

http://gorm-braarvig.blogspot.com/2005/11/access-database-from-sql-200564.html

 

G.

Answer 6

thanks.
how to setup Borland Database Engine (BDE 5.11) with ODBC?

Answer 7

 

Thak you guys. Really, the tip about sysWoW64 directory works.

 

Regards,

Thiago

Tritech Informatica - Consultoria e Desenvolvimento de Solucoes em TI

Answer 8

THis help me out alot!

thanks!

paul

 

 

Answer 9

"Windows\SysWOW64\odbcad32.exe" is the Best & the Shortest way, it should be added to the FAQs

thanks man for your help

---

Eng. Eslam Badawy

Answer 10

hey
i tried running Windows\SysWOW64\odbcad32.exe on my vista.
it worked for the first time, but i did not create any connections then.
i tried running it for the second time, it does not work and the drivers still are showing as un-installed.
Can you tell me what I am doing wrong?

Answer 11

I'm having the exact same problem (no MS Access Driver showing up, despite me installing Office 2000 on the machine) and yet when I run Windows\SysWOW64\odbcad32.exe I get the same result, which is that I'm told the Access driver hasn't been installed.  I'm on Vista (this all worked on my previous machine, which was running Windows XP).  I'm at the point where I'm thinking of switching to using MySQL instead of Access, just so that I don't have to figure out what's changed in the O/S on every new machine I get, as that's beginning to get very old, very quickly.

Answer 12

Add me to the list... unable to use ODBC driver on Vista 64.    This is ridiculous that this was changed so drastically..    I have tried using the 'other' tool mentioned to configure but it does not work either.  If I create a DSN and do a simple test connection it works.  However if I go into VS.net 2008, create a new basic project, add a connection to an access database, it fails with the standard:

************* Exception Text **************
System.InvalidOperationException: The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.
   at System.Data.OleDb.OleDbServicesWrapper.GetDataSource(OleDbConnectionString constr, DataSourceWrapper& datasrcWrapper)
   at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
   at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup
****************************************

That was one of the errors... however I finally read another post that I did not see before...   If anyone is still having problems with this issue, and the 'other' tool does not resolve it for you, then do what I did because it worked...  basically as another post says, change the compiler advanced options from AnyCPU to x86 and then compile!

For me that took care of the problem all around so far...





Malakie