FIX: FoxPro Not Releasing System Resources or Memory

 Last reviewed: October 14, 1997
Article ID: Q107516
2.50 2.50a WINDOWS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, versions 2.5 and 2.5a

SYMPTOMS

When a READ command is active in FoxPro for Windows and FoxPro is closed through the Windows Task List, the computer hangs when you try to quit Windows.

CAUSE

When FoxPro is closed under these circumstances, it does not release system resources or memory.

STATUS

Microsoft has confirmed this to be a problem with FoxPro 2.5 and 2.5a for Windows. The problem was corrected in FoxPro version 2.5b for Windows.

MORE INFORMATION

Steps to Reproduce Problem

  1. In Windows Program Manager, choose About from the Help menu and note the percentage of system resources available.

  2. Load FoxPro for Windows.

  3. Quit FoxPro.

  4. Check the percentage of system resources available. The amount should be the same as shown in step 1.

  5. Load FoxPro for Windows.

  6. In the Command window, issue the following commands: 

          @ 10,10 GET test DEFAULT SPACE(10)
      READ

  7. Press CTRL+ESC to open the Windows Task List.

  8. In the Task List, select FoxPro for Windows, and choose End Task to close FoxPro for Windows.

  9. Check the percentage of system resources available. The amount should be lower than those shown in steps 1 and 4.

Additional reference words: FoxWin 2.50 2.50a buglist2.50 buglist2.50a
fixlist2.50b
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxtoolGeneral
Keywords : FxtoolGeneral kbbuglist kbfixlist kbprg
Version : 2.50 2.50a
Platform : WINDOWS
Solution Type : kbfix

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