BUG: FormName Not in Correct Order After Out of Memory Error

Last reviewed: June 21, 1995
Article ID: Q76983
The information in this article applies to:

- Standard and Professional Editions of Microsoft Visual Basic for

  Windows, versions 2.0 and 3.0
- Microsoft Visual Basic programming system for Windows, version 1.0

SYMPTOMS

If, when creating a new form, you receive an "Out of memory" error message, no form will be loaded. However, the default FormName is still incremented by 1 so that when a new form can be created (for example, by deleting an already existing form) after getting the error, the FormName of the newly-created form is not in the correct sequence.

STATUS

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

MORE INFORMATION

Steps to Reproduce Problem

  1. Start Visual Basic or choose New Project from the File menu (ALT, F, N) if Visual Basic is already running. Form1 is created by default.

  2. Create new forms by choosing New Form from the File menu (ALT, F, F) until you get an "Out of Memory" error. On one machine, this occurred when trying to load Form52. In Visual Basic version 2.0, this may not occur until you reach Form100 or more.

  3. Choose the OK button to acknowledge the error message.

  4. Delete Form51 (or whatever the final form is) by choosing Remove File from the File menu (ALT, F, R).

  5. Create one more form. Form53 will be the next form, even though Form52 was never created.


Additional reference words: buglist1.00 buglist2.00 buglist3.00 1.00 2.00
3.00
KBCategory: kbenv kbbuglist
KBSubcategory: EnvtDes PrgOptMemMgt


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: June 21, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.