I found the following page to explain this irregularity. Now what's interesting here is that although the key Driver32 is used, the value points to the C:\Program Files\ path as opposed to the C:\Program Files (x86)\ path, thereby associating the Driver32 to the 64-bit drivers.
#Informix odbc 32 bit driver drivers#
The ODBC.INI file is located at C:\Windows\ where the contents of that file lists the same data sources as those displayed in ODBC Administrator, and includes the key/value pair of the 32-bit drivers for each of those data sources Driver32=C:\Program Files\IBM\Informix\Client-SDK\bin\iclit09b.dll. %systemdrive%/Windows/ System32/odbcad32.exe %systemdrive%/Windows/ SysWoW64/odbcad32.exeĬounterintuitively, the 64-bit ODBC Administrator is found at The 32-bit ODBC Administrator is found at
#Informix odbc 32 bit driver driver#
Both locations have the same number of data sources with the same names and same key/value pairs, with the exception of the Driver key which points to it's respective driver location C:\Program Files\ or C:\Program Files (x86)\. This essentially lists all of the data sources and their connection details.
I'm was unsuccessful at finding any sort of guide or walk through online, however I did find bits and pieces which could lead to the solution. Currently trying to setup a development environment which can handle both 32-bit and 64-bit ODBC Informix Drivers.
0 kommentar(er)
