Re: MS Access 2003: Linked Tables
Richard Spitz found that IDS 7.31 tables would link into MS Access 2003 only after replacing the newer Informix ODBC driver DLL (I-Connect 2.81.TC3) with the 2.81.TC2 one. Ben Thompson reported an OLE DB memory leak when updating blobs, still present in 2.90.TC1. scottishpoet identified it as bug 169500 and said running the coledb.sql script should resolve it, asking if he had.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Dear Informixers, a while ago I posted a question about a problem linking IDS 7.31UD8 tables into MS Access 2003 using the Informix ODBC driver from I-Connect 2.81TC3. This driver is in the file "iclit09b.dll" in the INFORMIXDIR\\bin directory and has version # 3.82.0.11811. In the meantime, I found that the ODBC driver from the previous Connect version 2.81TC2 works; it has version # 3.82.0.11600. Just copying the older dll over the newer one did the job. I still wonder why IBM/Informix cannot get their act together and supply ODBC drivers that just work. From sporadic postings in this group, I gather that even the ODBC driver from the newest 2.90 program suite still has problems, especially with Access. However, from the low number of postings about this topic, I assume that not many peoply bother using Informix's driver... Regards, Richard
Richard Spitz wrote: > I still wonder why IBM/Informix cannot get their act together and > supply ODBC drivers that just work. From sporadic postings in this > group, I gather that even the ODBC driver from the newest 2.90 > program suite still has problems, especially with Access. However, > from the low number of postings about this topic, I assume > that not many peoply bother using Informix's driver... I don't use the ODBC drivers with Access so can't comment on your original problem. I somewhat agree with the sentiment about CSDK. We have a serious problem with updating blob values through OLE DB where the driver leaks memory very quickly and the executable performing the operation can grow to hundreds of megabytes within seconds. It was confirmed as a bug in 2.81 when we had direct access to IBM Technical Support. It's still a problem in 2.90.TC1 and we are trying to get OpenPSL to exert what pressure they can on IBM to fix it. Whether our experience is typical or not I don't know. Ben.
ben, do you have the bug number?
There was a CSDK problem related to a memory leak.This is bug 169500. This problem should be resolved if you run the coledb.sql script. Do you know if you have run this script?