>Hi Linda,
>
>>Thanks Vlad, However, I would guess that procedures do not go into memory when a native object is instantiated. For example, if I instantiate an object and then try to access the VCX, I am locked out...this implies that FoxPro is "using" the VCX table as a table and not copying all the data somewhere else.
>
>VFP opens all class libraries that are needed by an instantiated class in datasession 0, the so called system-datasession. The VCX is opened in shared mode, but since its open in a different datasession, you can't open a VCX exclusively once it has been loaded.
>
>However, what VFP internally uses is a memory structure that is created the first time a class is loaded and duplicated for each instantiated object.
>
>Christof

If VFP is using a memory structure internally, why does it need to keep the VCX open?