Hi Bob:
Thanks for you reply. I'm not sure either what it all involves.
I can, however, tell you that VB was able call a RecordSet (oRS) thru the VFP written DLL. VB could do a oRS.Addnew, then oRS.Update. I guess this is what you meant Bob (yes?). It was great how it just worked though!!! I stil would like to include the oRS.Addnew and oRS.Update type of functions in the VFP's DLL. I still have not tried sending a oRS back to the DLL so maybe I can't do a oRS.Update with a VFP written DLL. This ADO thing if quite exciting.

Mal

>>Will the following work in a DCOM oject?
>>
>>*DCOM object
>>LPARAMETERS oRS
>>LOCAL oRecordset
>>oRecordSet = oRS
>>oRecordSet.Update
>>
>>hmmm I feel something is missing ... anyway, will the DCOM accept oRS as a recordset?
>
>Yes.. but I don't think you even have to do that. If you create a Client Side RecordSet in your middle tier and pass it to your IU tier... your UI tier can call the Update of the RS that will marshal the RS to the server which will do the update. I think this is part of ADO.
>
>Could be wrong, I only yhave played with it a little.
>
>BOb