FIX: CANCEL After "Object in Use" Error Closes Visual FoxPro

 Last reviewed: October 29, 1997
Article ID: Q135385
3.00 WINDOWS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft Visual FoxPro for Windows, version 3.0

SYMPTOMS

After suspending an error, using the CLEAR ALL command produces this error: 

   Cannot clear the object in use.
Using the CANCEL command after this error causes Visual FoxPro to close (crash). This happens only after using a version 2.x READ WHEN command.

WORKAROUND

There is no problem if you reverse the command sequence: 

   CANCEL
      * Click OK to clear the "Cannot clear object in use" error message.
   CLEAR ALL

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Visual FoxPro 3.0b for Windows.

MORE INFORMATION

Code to Reproduce Problem

DEFINE WINDOW one FROM 1,1 TO 20,20 FLOAT ACTIVATE WINDOW one @ 1,1 GET x DEFA 1 NAME bob READ WHEN test()

PROC test 

jhjhj            && Random characters to generate error
* When the error dialog appears, select SUSPEND * In the Command window, enter the following lines of code:

CLEAR ALL 

   * Click OK to clear the "Cannot clear object in use" error message.
CANCEL

Additional reference words: 3.00 VFoxWin fixlist3.00b buglist3.00
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxprgGeneral
Keywords : FxprgGeneral kbbuglist kbfixlist kbprg
Version : 3.00
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 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.