Hi Charlie:
That's about what I thought I'd have to do. I just have to figure out how to pass oRecordSet from a DCOM to the front end, then, back from the front end to the DCOM. I'll use the VFPCOM.COMUTIL to convert the recordset to a VFP cursor, then convert back using same. However, I can't experiment with DCOM yet because I ordered SP3 and am still waiting.

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?

Thanks for you help Charlie.

Mal


>If you want to access your VFP COM object through DCOM you have to pass your data to the client as an ADO RS. If you want to use VFP on the client too, you will have to convert the RS to a cursor on the client end. Some VFP native controls will not bind to ADO RS. One workaround is to use ADO compatible ActiveX controls on your VFP forms, then you won't have to convert to a cursor, or use a VB front end. When your done editing on the client, convert back to ADO RS and marshall changes back to COM object and update server.
>
>All of your validation is still in the middle tier, the front end is just a presentation layer.
>
>Charlie