I have something similar. When I inspected what I have I didn't have CANCEL. so I thought I would add it. But of course, with CANCEL, none of the subsequent commands run!

>Here's what I have tied to my F4 key and use frequently to wipe my dev environment free of references and anything that's open:
>
>CANCEL
>CLEAR ALL
>CLOSE ALL
>RELEASE ALL
>CLEAR PROGRAM
>CLEAR
>SET CLASSLIB TO
>SET PROCEDURE TO
>
>If all you want to do is clear everything the above does it. Otherwise you can selectively play around with the options. CLEAR ALL should release all object references even still referenced instances in which case you might get errors. SET STEP ON before CLEAR ALL is a great way to find hung references as the debugger will typically step into the Destroy of objects that are then releasing.
>
>+++ Rick ---
>
>>In the FoxPro IDE, I have a tool that is a .APP file. Whenever I have run the tool once in a session, and then exit the App (but I remain in the FoxPro IDE), then FoxPro still seems to have the .app file opened, or locked, or something.
>>
>>The result of this is, for instance, I cannot "DELETE FILE MyTool.app" from the command window, nor can I rename or delete the .app file from a Windows Explorer window. In both cases, I get an access denied error. Again, this true even after I exit the .APP (but, again, I still remain the FoxPro IDE). Don't ask why I want to delete it, just believe me that I need to.
>>
>>This proves that FoxPro still has a lock on the file, even after quiting the .app. The only way I have have to free it is to exit FoxPro. Only then can I delete the .app file.
>>
>>So, how can I tell the FoxPro IDE to "Release" this file?
>>
>>I tried RELEASE ALL, but that does not worlk.
>>
>>Any ideas?