1. ODBC driver installation conflicts (between 16 bit and 32 bit drivers) on NT
: Hi there,
: we've installed the Oracle ODBC driver two weeks ago (the one which
: came with the Oracle Workgroupserver 90 day trial edition). After we
: deinstalled this we have trouble installing Microsofts new ODBC
: drivers. I guess the trouble lies in the conflict that there are two
NT supports both the 16bit ODBC subsystem, which uses the usual config
files (ODBC.INI and ODBCINST.INI), and the 32bit subsystem, which
uses the registry.
To get rid of 16bit files, examine the .INI files and delete all
.DLLs specified by the various settings for the appropriate drivers,
then remove the driver entries from both ODBC.INI and ODBCINST.INI.
To get rid of 32bit files you'll need to use REGEDT32 and find the
appropriate ODBC entries. Remove the .DLL files specified by
the ODBC entries, then remove the registry entries. The usual
caveats re: mucking with the registry apply.
Oracle's workgroup drivers are 16bit, if I remember correctly, so
they should be installed using the appropriate version of ORAINST. Any
32bit drivers are best installed either using the 32bit version of
ODBCADM or through the control panel ODBC applet - if the driver
diskettes include an ODBC.INF file. If they don't, you'll just have
to trust that the installation program uses the 32bit routines...
Fax: +358 0 33 88 22 " Why me? "
2. OLAP Definition - Debate continues
3. Postmaster help output
4. corruption of 16 bit db when used by both 16 and 32 bit apps
5. How to query remote database?
6. 16 bit app. vs 32 bit ODBC
7. 16-bit ODBC v2.0 from 32-bit NT APP
8. Migrating 16-bit ODBC DLL (SQLServer) to 32-bit ODBC DLL (MS Access)
9. Connect 16-bit VB app to 32-bit Access 97 DB
10. 16-bit/32-bit ODBC drivers - NT Environment
11. 16 bit ODBC drivers in the 32 bit environment