>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....
>

Let me try a scenario:

SELECT * FROM customer INTO CURSOR temp

How will VFPCOM see that temporary cursor in order to USE it?