>>>Sorry, no. The fact that VFPCOM uses an alias name, and not the table from disk means that VFPCOM is DIRECTLY accessing data from the calling process. Otherwise, how can it scan the table to grab the values? Remember, the cursor in question may not live on disk at all- it may only live in VFP's memory space.
><<
>
>Right, via the LCK...


Ahhhhh- a breakthrough.

The LCK is what I was referencing when you stepped in and said there was nothing special going on, it's just a COM server. A COM server that calls VFP API methods is not any old COM server, because it can't be called from any old COM client. Not exactly magic, but definitely strays from strict COM standards, which is the point I started this thread with.

Whew. Glad we understand each other.