BUG: Menu Manager Internal Consistency Error When Build Screen

Last reviewed: April 30, 1996
Article ID: Q123207
The information in this article applies to:

- Microsoft FoxPro for Windows versions 2.5, 2.5a, 2.5b, 2.6, 2.6a

SYMPTOMS

Generating a screen when its corresponding .SPR file is open causes the following error if additional .SCX files are also open:

   Menu Manager Internal Consistency Error

WORKAROUND

Close the .SPR file before generating the screen. If there is a chance that the .SPR file may be left open, close any other open .SCX files.

STATUS

Microsoft has confirmed this to be a problem in FoxPro versions 2.5, 2.5a, 2.5b, 2.6, and 2.6a for Windows. 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. Connect to the CUSTOMER.DBF database by using the USE command.

  2. Create a quick screen. Then save it as TEST.SCX, and generate it.

  3. Open the TEST.SPR file.

  4. Open another <screenname>.SCX file.

  5. Generate TEST.SCX.

  6. Press a key to continue after the "File in use" error. Now you'll see error, "Menu Manager Internal Consistency Error," which is usually followed by a general protection (GP) fault.

    NOTE: The correct behavior is the redisplay of the Generate Screen dialog.


Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60 2.60a buglist2.50
buglist2.50a buglist2.50b buglist2.60 buglist2.60a gpf
KBCategory: kbtool kbbuglist
KBSubcategory: FxtoolSbuilder


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