Article ID: 308644 - View products that this article applies to.
This article was previously published under Q308644
This article has been archived. It is offered "as is" and will no longer be updated.
If your Visual Basic application includes Visual Basic intrinsic controls (such as TextBox controls) on the form, when the code repeatedly binds a Recordset object to the control with the DataSource property of the control, you may notice that memory usage grows while the application runs.
This problem occurs because the Recordset object is not released even if you set DataSource to Nothing.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
Note You must have a Visual Studio license agreement to obtain this hotfix.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote 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 usual 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 Time Version Size File name ---------------------------------------------------- 25-Sep-2001 8:03 220.127.116.11 1.33 MB MSVBVM60.dll 25-Sep-2001 8:03 18.104.22.168 1.79 MB VB6.exe
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Steps to Reproduce Behavior
Contact us for more help
Connect with Answer Desk for expert help.