I've seen this when classes are instantiated with NEWOBJECT() passing the
application name as the third parameter or when the IN clause is used with
SET CLASSLIB. You could run the code from my security session to peek into
the system datasession whether there's any VCX open.

When you clear classes you might need to clear them repeatedly as you can't
clear a class when a sub class is still loaded.

I assume you can't simply run CLEAR ALL / CLOSE ALL as you need to do this
as part of a process in the IDE?

In that case another approach is not using the APP in the first place. In
one of my application the user can edit an external VCX class while the
class is loaded. The way this works is that I make a copy of the VCX in a
temporary directory and load this one at runtime instead. After editing I
just remove the object and make a new copy.

Could a similar approach work you my making a copy of the APP into a temp
directory and executing it instead?

Christof

On Fri, Oct 14, 2011 at 4:56 PM, Matt Slay <[email protected]>wrote:

> 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.
>
>


--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/CAL4QJhjwP2RgYp8+ms-ddD_Lh2P5tiOxof1=ni5nvw7iqab...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to