FIX: Memory Leak When Field in Recordset Has More Than 16K of Data (236574)
The information in this article applies to:
- Microsoft OLE DB 2.1
- Microsoft Data Access Components 2.1
- Microsoft Data Access Components 2.1 (GA)
- Microsoft Data Access Components 2.1 SP1
This article was previously published under Q236574 SYMPTOMS
When using a Recordset that has been created by appending fields to a Recordset object (a "creatable" recordset), and when any text fields in the recordset contain more than 16K of data, a memory leak occurs when setting the value of the field.
The memory leak occurs regardless of what the field's Size property has been defined to be, as long as the size of the actual data is more than 16K.
CAUSE
When the amount of data being assigned to a field value is more than 16K, the Data Conversion Library creates a scratch buffer to work with. The buffer is not released.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Data Access Components Service Pack 3 that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Version Size File name
-------------------------------------------
7/2/99 02.10.4302 359KB oledb32.dll
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem has been fixed in Microsoft Data Access Components version 2.5.
Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbADO210fix kbbug kbfix kbMDAC250fix kbMDACNoSweep kbQFE KB236574 |
---|
|