utter77
asked on
How do i create 32 bit ODBC driver on 64 bit system
Hi.
I have an old system that uses system dsn odbc drivers and it won't work on 64 bit windows.
If I create an ODBC with odbcad32.exe in system32 i get a 64 bit driver whitch won't work
and if i create an ODBC driver with odbcad32.exe in syswow64 i get a 32 bit driver that the system can't find.
How do I solve this?
I have an old system that uses system dsn odbc drivers and it won't work on 64 bit windows.
If I create an ODBC with odbcad32.exe in system32 i get a 64 bit driver whitch won't work
and if i create an ODBC driver with odbcad32.exe in syswow64 i get a 32 bit driver that the system can't find.
How do I solve this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Tell us more about the type of file/database that you're connecting to. For example, if you're using ODBC to get to a Microsoft Access or Excel file, then that's just not gonna work... as the ODBC driver is reliant upon another driver that doesn't exist (yet) in the 64-bit world
ASKER
I will connect to SQLServer and Oracle.
What type of application is this... can it be set to run in the 32-bit mode (similar to the way to can control the "bitness" of a .Net application)?
ASKER
This is an old VB6 application. I cannot change anything in it. It runs fine under 32-bit systems.
So, tell us more about " if i create an ODBC driver with odbcad32.exe in syswow64 i get a 32 bit driver that the system can't find"
Are you saying that if you create a system DSN using the "Microsoft ODBC Driver for Oracle", then your VB6 application can't find it?
Are you saying that if you create a system DSN using the "Microsoft ODBC Driver for Oracle", then your VB6 application can't find it?
ASKER
The old VB6 application looks for system DSN ODBC drivers in the normal location in the registry. However, if you create a system dsn on a 64-bit system with the tool found under system32 you end up with a 64 bit driver located in the normal location in registry. Then the application will find a 64 -bit driver. And if you create a driver with the tool foound under syswow, you will end up with a correct 32-bit driver but it is located in a syswow node in the registry.
I tried to create a 64 - bit driver for SQL and it seems to work. I get a "can't open view..." error from the app.
I tried to create a 64 - bit driver for SQL and it seems to work. I get a "can't open view..." error from the app.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.