Memory leak in Client SDK with OLE DB connections when updating blobs (was: [Re: MS Access 2003: Linked Tables])
- From: Ben Thompson <ben@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Jul 2005 10:01:02 +0100
I can now confirm that running the coledbp.sql against sysmaster has fixed our problem and our application using CSDK no longer leaks memory. For the benefit of anyone else, the coledbp.sql script is distributed with Client SDK for Windows (I am using 2.90.TC1) and lives in the etc subdirectory. It seems from our point of view that it would be a great idea to create the tables in the coledbp.sql script in the sysmaster database shipped with IDS. Many thanks for this, it solves a lot of issues for us.
Ben. .
- Follow-Ups:
- References:
- Re: MS Access 2003: Linked Tables
- From: Richard Spitz
- Re: MS Access 2003: Linked Tables
- From: Ben Thompson
- Re: MS Access 2003: Linked Tables
- From: scottishpoet
- Re: MS Access 2003: Linked Tables
- From: scottishpoet
- Re: MS Access 2003: Linked Tables
- From: Ben Thompson
- Re: MS Access 2003: Linked Tables
- Prev by Date: Re: Alter table
- Next by Date: Re: Memory leak in Client SDK with OLE DB connections when updating blobs (was: [Re: MS Access 2003: Linked Tables])
- Previous by thread: Re: MS Access 2003: Linked Tables
- Next by thread: Re: Memory leak in Client SDK with OLE DB connections when updating blobs (was: [Re: MS Access 2003: Linked Tables])
- Index(es):