Why are are fixated on the COM Server having access to the calling process's private datasession is beyond me. A COM server can USE a cursor, and through VFPCOM, marshal records to an ADO Recordset. It is THAT ADO Recordset that is passed back to the calling process. The calling process then does SOMETHING with the data in the ADO Recordset, either directly or by converting back to a VFP Cursor. Once the calling process is done, it can marshal that data BACK to an ADO Recordset. That ADO Recordset in turn can be sent to a method of a COM Server that will update the back end.

That is the most basic I can make the scenario....


>>There is no magic. VFP COM components cannot "see" VFP cursors in other data sessions or other components. I still do not see what the big deal is. Follow this scenario:
>>
>>VFP Component serves up data:
>> 1. Open Data
>
>Sorry if I'm being dense here John. Please explain this step. How does a COM server "open" data?
>
>Actually, it would be most helpful if you could put together a quick code example that could be used in a VFP COM server that would make use of data from the calling process' datasession.