Robin Abecasis
July 23rd, 1998, 10:44 PM
Has any-one come across a memory leak when using ODBC v3 (or higher), when using multiple CRecordset objects which are continually opened, requeried and closed?
Cheers,
Robin
Cheers,
Robin
Click to See Complete Forum and Search --> : ODBC v3 memory leak?
Pete Barnfather
July 30th, 1998, 12:01 PM
I have been working with MFC and ODBC for about three years now and am afraid to say that I have come across a number of serious bugs in ODBC.
These usually manifest themselves at random and would give the impression of being memory leak releated.
Microsoft are fully aware of these problems and have documented them on their Technical Support pages.
My recommendation would be you upgrade to ODBC 3.5 as soon as you can, this fixes a number of memory releated problems specifally related to open multiple recordsets and performing open, update and close operations. (See Microsoft Technical Article Q173513)
Another note of interest is Microsoft Technical Article Q185864. This gives details on modifying the CRecordSet base class to work around a memory exception which can occur when SQL statement lengths do not fall on word boundaries.
Good luck!
These usually manifest themselves at random and would give the impression of being memory leak releated.
Microsoft are fully aware of these problems and have documented them on their Technical Support pages.
My recommendation would be you upgrade to ODBC 3.5 as soon as you can, this fixes a number of memory releated problems specifally related to open multiple recordsets and performing open, update and close operations. (See Microsoft Technical Article Q173513)
Another note of interest is Microsoft Technical Article Q185864. This gives details on modifying the CRecordSet base class to work around a memory exception which can occur when SQL statement lengths do not fall on word boundaries.
Good luck!
codeguru.com
Copyright 2007 Jupitermedia Corporation All Rights Reserved.
Copyright 2007 Jupitermedia Corporation All Rights Reserved.