If you created in instance of class foo, then were able to modify class foo in the class designer while that instance existed, then created another instance of class foo, the two instances would not be of the same object, plus the caching system would likely have to be all modified to allow this behavior, and it would be likely performance would suffer because of it. I see this thread trying to understand how classes are cached, but I haven't figured out why it matters so much, or if there is some ER or change of behavior desired for a specific/explained reason.

Ken

>That explanation doesn't fully answer why it might be bad to change the VCX while an application is using the same class from a cached memory structure. I hazard a guess that it's because there may be times when the executing VFP app. may well need to re-load the class. Say, for instance, if memory got low or someone issued a SYS(1104).