Tracy - if I understand you right - no, I am doing it all in one session. As for Classes - nope, as the system is all based upon older type code and PRG - much of the system is still a carry over from the DOS. Although we work in VFP - most of the system still looks like FPD.
But, yeah - my workaround seems to work for now! Seems to me that VFP didn't like me doing a "suspend" - although its really that I have Set Step on - and then ran my separate program while still in stepping mode. L8r, -K- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tracy Pearson Sent: Thursday, September 03, 2009 3:16 PM To: [email protected] Subject: RE: VFP has a STRANGLEHOLD on My FXP... It sounds like you are editing the PRG in one VFP session, and testing it in another. If you have a class defined in the PRG the FXP will be held by the testing session. To clear it after the object (or objects) is released, you will need to CLEAR CLASS {classname}. Where {classname} is same as DEFINE CLASS {classname} AS ???. If you have subclasses, you need to work your way down to the parent if it exists in this PRG. If your PRG creates a private datasession, which you have opened a table in it in a BROWSE window, the datasession and FXP will remain locked until you close the BROWSE window. The last thing, after all the CLASS and DATASESSIONS have been closed, you need to CLEAR PROGRAM in the testing session. I recently went through similar things myself and found this cleared things up. I do see you've found a way to work with everything in the same session though. HTH in the future, Tracy -----Original Message----- From: Kurt Wendt Sent: Thursday, September 03, 2009 11:40 AM OK - yeah - that Subject line is meant to be humorous - but, the problem I'm having is real - and a Good Bit annoying! I have this program I am working on. However, It must eventually run from Within this large system of ours. Funny thing is - its kind of related to the current "VFP9 - Set Relation" thread - as its mostly a FPD type app - although there are actually some screens in the App that are VFP/graphical screens. So - to test this program I am working on - I have a suspend in the main application (or rather - one of the sub-programs) - and during the suspend I am running my small program. I do this because our system is Filled with Public Var's (and, yeah - I read the other thread where people discussed the Evil Side of using Public Var's - although this system here existed WAY before I ever showed up on the scene). Well, my small program runs fine, and within it there is a Return statement - which should be Exiting me out of my small program. (Also - FYI - this small program is a Copy of another pre-existing program in the larger application - which I am re-purposing for a new functionality.) The problem is that even after I completely exit the full application - and I am back at the VFP command window - it seems that VFP still has a Hold on my FXP. If I try to recompile my PRG(VFP says "Cannot create file...fxp"), or even just try to Delete the FXP(VFP says "File is in use." - I can't. Even though I issue Clear, Clear All and Close All - I still can't do it. And, needless to say - when I try to test the program again - its running the prior version (the FXP) as opposed to the newest changes (in the PRG). My only option to resolve the problem is to Completely Quit from FoxPro. But, that's a real Pain - to have to do it after EACH test - and then to Startup VFP again! I'm Stumped... -K- [excessive quoting removed by server] _______________________________________________ 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/289ea162f5642645b5cf64d624c66a1405578...@us-ny-mail-002.waitex.net ** 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.
