Logiciel Edition Etiquette Code Barre Gratuitous Space. Contains links to download DB2® 9.7 Fix Pack 11, servers, extenders, clients and drivers from Fix Central for AIX, HP-UX, Linux, Solaris, and Windows operating systems. Compatibility, Any tool that needs to connect to the Connection 2.1(1) or later database needs the IBM Informix drivers installed to be able to connect. Each tool that. Download Now (ZIP file - unpack and run install). I've tested the 4.10 TC6 install on 64 bit versions of Windows 7, 8.1 and 10 with no issue.

In order to use a 32 bit ODBC driver on a 64 bit Windows machine, it has to be configured using a 32 bit ODBC Administrator which is not visible through normal Windows menu options. Utilities for 32 bit operations are found in the C: Windows SysWOW64 directory. As a prerequisite for a 32 bit IBM Informix CSDK installation to proceed correctly, add the SysWOW64 directory to the system path, as follows: • Run 'C: Windows System32 control.exe system' • Select Advanced system settings from Control Panel Home • On the System Properties Panel that appears, • Select: Advanced tab->Environment Variables • In the System Variables window under Environment Variables, • Select and edit the PATH variable. Prefix the PATH list with 'C: Windows SysWOW64;' Proceed with the IBM Informix CSDK product installation.

The suggested install directory for 32 bit CSDK is 'C: Program Files (x86) IBM Informix Client SDK'. Once the CSDK installation is completed, access the ODBC administrator utility located at 'C: Windows SysWOW64 odbcad32.exe'. Now, when you access the Drivers Tab of the ODBC Administrator, the IBM Informix Driver is visible. This is the one you want to use.

At this point, you can proceed with normal configuration. Related information.

I am trying to create a linked table in a 64-bit SQL Server to Informix, and the SQL server does not list Informix ODBC in the DSN list. I have downloaded the 64-bit Informix Client SDK, however, despite the fact that it states 64-bit Informix Client SDK, it only appears in the 32-bit ODBC DSN.

I tried to create a linked table in a 32-bit SQL Server and I was then able to see Informix ODBC DDN. I was just wondering that if there is an Informix Client SDK that would show in the 64-ODBC DSN, not the 32-bit? Also is there a way of linking a 64-bit SQL Server to Informix please? Did you use the 64 bit version of ODBCAD32.EXE to create the DSN? There are two versions of the ODBC administrator. This one is the 32 bit version: C: Windows SysWOW64 odbcad32.exe It can only see 32 bit drivers, and only 32 bit processes can see it's DSN's This one is the 64 bit version: C: Windows System32 odbcad32.exe It can only see 64 bit drivers, and only 64 bit processes (i.e. SQL Server 64 bit) can see it's DSN's Even better you could define a DNS-less connection which doesn't use a DSN, it uses the driver directly.

Then you can avoid this confusing step altogether. I would have used the Comment feature, but I do not have enough 'Reputation Points' to do so. The answer of SGeis, above, is on the money.

It was hard for me to find such a clear, straightforward answer. Snapshots of the dialog boxes help immensely. Let me add to his answer the following: • The Data Source fill-in (YourDatabaseName@YourInformixServerName) could be something as simple as Fred@Barney, rather than what I tried, namely, Fred@199.188.77.66 or Fred@199.188.2 (the latter specifies a port/service number). • Once you create the linked server, if you go back into its General properties page, you will see that you cannot edit what you typed for Linked Server, Product Name (Why isn't this called 'Provider Name,' since Ifxoledbc is listed under Linked Servers/Providers in the Object Explorer tree?), Data Source, etc. So, if your connection fails because you mistyped something, it is unclear how to fix it.

Here is what you may do: • Right-click the linked server. • Beneath 'Test Connection,' look for 'Script Linked Server as.' • Click the latter, and, then, each of the following: 'DROP And CREATE To' and 'New Query Editor Window.' • In the script text that appears, type replacement info for those settings that were grayed-out and uneditable. • Press F5 to run the script and thereby apply your changes.

In doing so, the existing linked server is dropped, and a new one is created. • Open up your linked server's Security properties page and re-enter any connection password (even though asterisks -- suggesting that the password is filled and correct -- may appear in the corresponding entry). Also, examine the General properties page. Make sure that your changes stuck. Even though you ran the script and received no error, SQL Server will blank out fill-ins such as 'Linked Server,' 'Product Name,' and 'Data Source' if, for example, you, as I did, had a brain aneurism and chose the wrong drop-down item for 'Provider.' • As noted above, click 'Test Connection,' to verify that your changes work. I was able to set up a linked server without Ifxoledbc.