nanaxbee.blogg.se - Informix odbc driver

#Informix odbc driver drivers
#Informix odbc driver driver
#Informix odbc driver windows

#Informix odbc driver driver

In the case of Informix, the driver for each architecture MUST be installed separately.

#Informix odbc driver windows

(%WINDIR%\SysWOW64\sqlsrv32.dll) on 64-bit Windows platforms. (%WINDIR%\System32\sqlsrv32.dll) and a 32-bit library Microsoft’s SQL Server ODBC driver installs both a 64-bit library Will fail with the "architecture mismatch" error. Source for a 64-bit ODBC driver, the connection will succeed if aģ2-bit version of the driver is installed. If a 32-bit application attempts to connect to a valid user data

#Informix odbc driver drivers

Simply put, a 32-bit application which connects to the 64-bit ODBC drivers will automatically be redirected to the 32-bit drivers based on the registry entries, whereas a 64-bit application will need no such redirection. System data sources that are returned are ones for 32-bit ODBC HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI, and the only HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI to So, forĮxample, when a 32-bit application calls SQLDataSources, the resultant Redirected to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node. Registry calls made to this key by 32-bit applications are Registry redirection affects the HKEY_LOCAL_MACHINE\SOFTWARE Portions of the registry and redirects them to another portion of the

The WOW64 registry redirector intercepts calls made to certain 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. 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 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.

64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.

32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI.

64-bit: C:\Program Files\IBM\Informix\Client-SDK\įrom what I can see, the registry entries for the drivers are located at:.

32-bit: C:\Program Files (x86)\IBM\Informix\Client-SDK\.

The drivers are installed at the following locations (based on the registry entries) I can't seem to find versions 3.70.TC3 or 3.70.FC3, but I did find 3.70.TC7 and 3.70.FC7 directly from the IBM website, which I assume are just slightly updated versions. I'd just like a little more advice to ensure I'm on the correct path. 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.