>>>>make a habit of following sequence
>>>>- modify a class/prg/form
>>>>- test it
>>>>- do env
>>>>- back to top
>>>>
>>>My question is: is it avoidable at the programming level?
>>
>>Yes, method described above
>>
>>I am doing this sequence for years now and have never had any problems since.
>>ie, before editing you have to release all instances of a class + clear any cache, reset lib, classlib, procedure, ... This is the only way I know to force vfp to discard it's internal cache and read all of it back from disc
>
>
>Well, my question was mostly: what causes this behavior and is where a way to prevent it? I switch between form and command window and do clear all, but it sounds a little bit inconvenient...

Cause: vfp's internal cache as far as I can see
Ways to prevent: clear the cache prior to editing forms/classes
Inconvenient: yes