🚀 go-pugleaf

Thanks for your reply, Val. I had previously read that article and
installed Jet 4.0 SP6 on both of my test boxes. The article is kind-of
vague about what the symptoms would be after the upgrade. But, in my
case, the program is still consuming memory at about 80% the rate that
the datbase grows. In the last 24 hours the database grew 1.51
megabytes and Peak Memory Usage has grown by 1.36 megabytes.

As for coding the work around anyway, I did not consider it since I
did what it indicated to do in the first case.

One thing I did do, was to write a test program (using the exact code
that I am using in the main app) that opens the database, writes 1000
records and closes the database. Using CodeGuard, I have confirmed
that my test app is not leaking memory. As a test, I stubbed out the
database call (so that all of the other code runs) in the test app and
am confident the leak is the database DLL or ADO. The test app leaks
memory just as it does in the main app.

Other notes:
* I have confirmed if I don't start the Database Thread, that the
program does not appear to 'leak' memory.
* Windows 2000, SP2. Jet/MDAC 4.0 SP6.
* DLL is in VC++ 6.0 with latest SP. Application is in C++ Builder 5,
latest Patches.

Thanks,

Paul Maia

"Val Mazur" <group51a@hotmail.com> wrote in message news:<uv12UZaKCHA.2552@tkmsftngp08>...
> Hi,
> 
> Check if this is not your case.
> 
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q247140
> 
> I think you would need to close your connection periodically to free you
> allocated memory
> 
> --
> Val Mazur
> Microsoft MVP
~snip~