BUG: DBGrid V1.0.093 Loses Resources in Windows 3.11

 Last reviewed: December 12, 1997
Article ID: Q173082
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions, 16-bit only, for Windows, version 4.0

SYMPTOMS

A resource leak can occur when using DBGrid control version 1.0.093 with the Visual Basic 4.0a 16-bit. The leak only occurs when you run the Design Environment Microsoft Windows for Workgroups 3.11.

RESOLUTION

You can reduce the resource leak by closing each open form before ending Visual Basic.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. From Program manager, in the Help menu in About Program Manager, choose About Program Manager. Note the system resources listed.

  2. Start and end Visual Basic 4.0a without saving the default project. From the Help menu in Program Manager, choose About Program Manager and note the system resources listed.

  3. Start Visual Basic and add two DBGrid controls to Form1.

  4. Resize each DBGrid control at least twice.

  5. End Visual Basic without saving the project.

  6. From the Help menu in Program Manager, choose About Program Manager. Note that the amount of system resources is reduced. 
Keywords          : EnvtDes vb416 VB4WIN
Version           : WINDOWS:4.0
Platform          : WINDOWS
Issue type        : kbbug

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 12, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.