BUG: Form Height Not Displayed Correctly in Design View

 Last reviewed: October 16, 1996
Article ID: Q150208
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

If the height of a form is re-sized to the height of the menu plus the title bar and then saved and closed, the height is shown incorrectly when the form is reopened and viewed in design mode. When the project is run, the form returns to its correct height.

STATUS

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

MORE INFORMATION

Steps to Reproduce Problem

  1. Start a new project in Visual Basic. Form1 is created by default.

  2. From the Tools menu, select Menu Editor to add a menu to Form1. In the dialog box, enter a Caption of File, a Name of "mnuFile," and click OK.

  3. Adjust the height of Form1 until it is the height of the menu bar and title bar only. Save the project and form.

  4. From the File menu, select New Project to clear out your existing project.

  5. On the File menu, select the project at the top of the most recently used project list, and then choose to view Form1 in Design mode.

Notice that Form1 appears, but its height is only that of the Title bar plus borders. Run the project by pressing F5, and Form1 is shown correctly even after the project is stopped.

Additional reference words: 4.00 vb4win vb4all buglist4.00
KBCategory: kbprg kbbuglist
KBSubcategory: PrgOther



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: October 16, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.