BUG: Screen Wizard Does Not Release Memory Handles

 Last reviewed: June 27, 1995
Article ID: Q114503
The information in this article applies to:
  • Microsoft FoxPro for Windows, version 2.6
  • Microsoft FoxPro for MS-DOS, version 2.6

SYMPTOMS

Memory handles appear to be used but not released from within FoxPro for Windows and FoxPro for MS-DOS when the following two conditions are met:

  1. A relational updatable query is created from within the Query Wizard and is made active.

  2. The Screen Wizard or Report Wizard is entered.

STATUS

Microsoft has confirmed this to be a problem 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

CAUTION: The following procedure can result in an "Insufficient Memory" error message after the steps have been executed numerous times (approximately 10). This procedure should not be performed without closing all other applications running under Windows first. This is a precaution, as a general protection (GP) fault will also occur eventually. Should a GP fault occur, quit and restart Windows before starting FoxPro again.

  1. Create a program containing the following line and add the program to your catalog: 

          WAIT WINDOW SYS(1011)

    This command will display how many memory handles you have used.

  2. With the Updatable Query Wizard, create an updatable query that relates three or four tables. For example, link INVOICES to CUSTOMER and DETAIL (these tables are in the sample catalog). Make the new query active by choosing the Use push button while the query is selected (highlighted).

  3. Run the program to show how many memory handles you've used.

  4. With that query still active, start the Screen Wizard.

  5. Choose Cancel in the first screen of the wizard.

  6. Check your memory handles again by running the program.

Note that the number of memory handles used has increased markedly. Continued repetition of the above steps will cause more and more memory handles to be used and will eventually result in an "Insufficient Memory" error message and then a GP fault.

Additional reference words: FoxDos FoxWin 2.60 gpf errmsg err msg
buglist2.60
KBCategory: kbprg kbtool kberrmsg kbbuglist
KBSubcategory: FxtoolWizscreen

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