Re: Please help with ODBC

Roland M'ller wrote: > > Hello, > > I am using I-Net for Windows 5.0.1 under Win 95. > > In order to use ODBC, I installed DataDirect (32-Bit) by Intersolv. > > Whenever I try to configure the Informix Data Source, the following > error appears: > > The setup routines for the INTERSOLV 2.11 32-BIT INFORMIX5 ODBC driver > could not be loaded. You may be low on memory and need to quit a few > applications. > > Ok, first of all I have a P-75 with 16MB Ram,l 64 MB Swap and no other > applications running. > > Second, according to the help file, this error indicates, that the > ODBC-Driver could not find ISQLI501.DLL, which is funny, because > it is where it should be, is included in the PATH, plus the > INFORMIXDIR-Variable is set.CLIPPED... Roland, I have run into this problem also. After many hours of trial and error, I have discovered that the version of ODBC will cause this problem also. The book says the path has to be set, etc. but sometimes when you intstall the ODBC drivers, the version of OBDC is not updated. I use the 2.11 drivers (INFORMIX5) - this corresponds to the version of I-Net that the driver is work with -- not the engine. Here is how to fix... Use the utility that Intersolv provides called DLL manager or something like that. While this application is active, open the odbc control panel to configure. You should see the odbc.dll and serveral other related odbc dll's become active. Double click on their entry, and you should see a screen that gives you the version of ODBC that you are running. You must be running 2.0 or greater, not the 1.5.1 or similar version that is probably being shown. Replace the ODBCADM.EXE, and all the ODBC.DLL's that you can find - I think there are about 3 of them. Once this is done, restart windows or reboot, and it should all work. I am under Win 3.1 and have different odbc, but I assume most of the inner workings are the same. Have fun - you will quickly find that ODBC is not all it is cracked up to be, but works fantastic for alot of quick and dirty uses. Ok, its really not that bad... James Saville BellSouth Telecommunications, Inc. andrew.saville@bridge.bellsouth.com <<These comments are my own and are based on my own experiences>>