Sometimes even CLOSE ALL, RELEASE ALL and CLEAR ALL won't even do it.
VFP's ability to clean itself up reliably deteriorated with each release
from VFP 7 to VFP 9. And in my experience, the problem is worst with VFP
9 on Win 7.
I do not know about it getting worse since I tend to use only a
small part of VFP, but sometimes, VFP gets messed up in some way. This
happens during debugging which is just when I want it to be resettable.
I think one of the big culprits is class libraries.
You've probably tested something, then opened a .prg class library and
attempted to edit the code, and received a message "Remove [something] from
memory?" This stuff is all supposed to be out of memory when whatever you
tested reaches the end of its stack on the way out. And it certainly should
not be in memory if what you tested concludes with the "big three": CLOSE
ALL CLEAR ALL RELEASE ALL. But this happens anyway.
And I think that issue is related to why stuff won't compile until you
issue those commands and sometimes not even then.
Folks are right about using a separate instance of VFP to compile or debug.
The reason I don't do that is because I get "access denied" if I have a
project open in the first instance that the second instance tries to open
again. (I know, I know, I should set my VFP IDE preferences to
multi-user... Old habits die hard.)
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** 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.
