BUG: Resetting IntegralHeight Causes General Protection Fault

 Last reviewed: May 6, 1996
Article ID: Q150238
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic, 16-bit only, for Windows, version 4.0

STATUS

If the IntegralHeight property of a list box is toggled from True to False or False to True after setting the Font of the list box to a different size and changing it to FontBold, a General Protection Fault occurs in Windows 3.11. On Windows NT 3.51, an Application error - Integer Divide by Zero - error occurs.

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.

WORKAROUND

Toggle IntegralHeight to the desired position and then change the Font properties for the list box.

MORE INFORMATION

Steps to Reproduce Problem

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

  2. Place a list box on Form1.

  3. Select the Font property for the list box, and press the ellipsis (...) adjacent to the property. In the Font dialog box, change the Font size to 12, and change the Font Style to Bold Italic. Click OK.

  4. Select the IntegralHeight property and change it to False.

On Windows NT, an "integer divide by 0" message occurs, and a General Protection Fault occurs on Windows 3.11. In one test, the address of the Fault is 000B:39F0 in module Vb.exe.

To make the necessary changes without causing a GPF, reverse steps 3 and 4.

Additional reference words: 4.00 vb4win vb416
KBCategory: kbprg kbbuglist
KBSubcategory: PrgCtrlsStd



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