MDAC 2.8 doesn't work in Windows XP 64 BIT

[sobase]

All,

Any body know what is the solution for the above subject. Recently we upgrade our OS to XP 64 BIT then some tool developed using MDAC2.8 component is no longger working...

I am looking forward for valuable answers..

Regards,

Sobase

[cluberti]

I believe that x64 SP2 already contains MDAC 2.8 SP2. You can run odbcad32.exe from a command prompt to see the x64 components (open a 32bit command prompt and run the command there to see the 32bit components).

[CoffeeFiend]

The issue you're having might also be due to a ODBC driver that isn't available on the x64 platform (e.g. Microsoft.Jet.OLEDB.4.0, for accessing older MS Access .mdb files)

Not many options in that case:

-not using Windows x64 for now (not a long term solution for sure)

-moving to another database that has a driver (newer MS Access 2007 format, SQL Server Express, etc)

[sobase]

I believe that x64 SP2 already contains MDAC 2.8 SP2. You can run odbcad32.exe from a command prompt to see the x64 components (open a 32bit command prompt and run the command there to see the 32bit components).

Cluberti,

I ran the command, there is no ODBC driver available there apart for SQL Server. Please see the attachment.

Our tool try to connect to ORACLE database through ADODB using MSDAORA.1 provider, has it anything to do with ODBC or just MDAC?

Please advice and thank for the help in advance.

Regards,

Sobase

[CoffeeFiend]

Our tool try to connect to ORACLE database through ADODB using MSDAORA.1 provider, has it anything to do with ODBC or just MDAC?

MDAC doesn't include ODBC drivers for Oracle, you have to install those separately.

See this page for a complete list of all their ODBC drivers (some of which are for 64 bit Windows)

[sobase]

If I run the commands (odbcad32.exe) under c:\windows\sysWow64, then I can see more driver in the ODBC admin window.

I guess I need to redirect to which ODBC my tool should use. But anybody know how to do this?

[cluberti]

If I run the commands (odbcad32.exe) under c:\windows\sysWow64, then I can see more driver in the ODBC admin window.

I guess I need to redirect to which ODBC my tool should use. But anybody know how to do this?

If your tool is 64bit it'll use the 64bit odbc components, and if it's 32bit it'll use the 32bit components. As you can see, there are far more 32bit than 64bit components.