But VFPCOM has to know about tables in the datasession of the process that called it. Normal COM components can't do that. Not even in-process ones. I understand fully how to pass around a recordset, or any other parameter or return value, but I don't know how to get a COM server to see and create tables through COM boundaries- this normally breaks the inherent encapsulation that COM gives us.

Either the answer to what I am asking is so simple and silly that I can't see it, or the VFP team pulled some pretty fancy magic to make it happen.


>I don't see where the confusion is... It is the ADO Recordset that gets passed from component to component or component to UI and vice-versa. In all of my ADO sessions, I always ask: "Have you ever wanted the ability to treat a table as a data type that can be passed to method procedures and functions?"
>
>That said, if I want a component to gain access to data, I am going to pass the data to the component via ADO. Alternatively, I could use XML.
>
>
>>Actually, it's not simple if you think about it- in CursorToRS(), how does the COM object see the table in the first place? In RSToCursor(), how does the remote process create a cursor in the local datasession?
>>
>>If you know how to create a COM object in VFP that can see the datasession of its caller, please enlighten us.
>>
>>
>>
>>>The idea is actually very simple. VFPCOM fabricates an ADO recordset with the same structure as the VFP table. The records from the VFP table are then marshaled to the new ADO recordset. Once that process is complete, the recordset is returned to the calling program.
>>>
>>>>I have been working with the VFPCOM utility for 2 weeks and have found that I do not get Numeric Values from a Recordset into a cursor using the RStoCursor() function. (Note: we are using Free tables) I decided to write my own DLL that will create a Cursor. Everything works if I make it a Function within my app. We (as a Company) want to create a DLL out of this. I now have my own CursorToRS() working in the DLL but I can not figure out how to create a Cursor from this DLL into the Calling Program. Does anybody know how the VFPCOM.DLL Creates a Cursor in the local sesion of VFP? I know you can not pass back a cursor.. is it using some Low Level stuff I am unaware of?
>>>>
>>>>Try to get more confuesed that this! Thanks to a anybody and Everybody.