My understanding of what actually goes on when something is cached is limited. I thought that a copy of what is cached was placed in memory. If that is true then a cached VCX table would not need to stay open because a copy of the table is in memory. But when you are referring to a "special way", do you mean that the table needs to remain open as part of the caching?

>There actually is some caching going on within VFP, which is why when you instantiate an object from a class (especially a VCX based class), then instantiate another one, the time it takes to instantiate the second instance is far faster than was the first. VFP does things to release caching either automatically or by user (modifying a class, etc.) so it is kind of an auto garbage collection within VFP on class caching. Yes the class is a memory structure internally, but the VCX table it was instantiated from is cached in a special way for pure performance reasons.
>
>Ken
>
>>If VFP is using a memory structure internally, why does it need to keep the VCX open?