BUG: Resource Loss with VB4 16-Bit OLE Container in Windows 3.11

 Last reviewed: November 5, 1997
Article ID: Q176162
The information in this article applies to:
  • Microsoft Visual Basic Professional Edition, 16-bit only, for Windows, version 4.0

SYMPTOMS

When using the 16-bit Visual Basic 4.0 OLE Container Control under Windows 3.11, a one time loss of System Resources will occur. For example, when inserting an Excel 5.0 Worksheet into the OLE Container, the first time that sheet is instantiated, Windows will incur a loss of approximately 3 percent of the available System Resources. This loss has been reproduced with other inserted objects as well, with varying amounts of System Resources being lost. This resource loss only occurs the first time that the inserted object is instantiated.

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. Add an OLE Container Control to Form1.

  2. Insert an Excel 5.0 Worksheet into the OLE Container.

  3. Compile this project into an executable file. Exit to DOS and restart Windows.

  4. In Program Manager, select "About Program Manager" from the Help Menu, and note the Available Resources.

  5. Start the executable created in step 3.

  6. Double-click the OLE Container.

  7. Press the ESC key to close the Excel Worksheet.

  8. Exit the Visual Basic program.

  9. Re-check the Available Resources and note that there is a loss of Resources. 
Keywords          : IAPOLE 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: November 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.