>>Q: Will using FoxPro ODBC on server let the client instanciate server xBase DCOM DLLs on serve DBFs and CDXs?
>
>RDS allows you to do this with the name space object.

This is good stuff! Thank you! More Q's:

1) Instance localy an RDS DataControl, and use it to manage the connections and time outs.
2) Build the DCOM components (as DLLs) and mount them on the server.
... Neat if DCOMs could xBase to "server back end" DBFs/CDXs! The DCOM Triggers would contain the necessary xBase, right?
The basic model
I. Local VFP Form instanciates RDS managing connection to server?
II. Remote DCOM gets instanced (oRemoteMyDCOM=CreateOject(MyDCOM.Application)), right?
III. Use xBase on Server (oRemoteMyDCOM) to populate cursor (at server). Use RDO/ADO to carry the cursor back to the client VFP form, right?

So, the spec for our mythical xBase Client/Server is like this (to date).
Client Stuff:
VFP Exe (ActiveDoc not required)
RDS Connect to server
Server Stuff:
NT
VFP Runtime
DCOM DLLs (that xBase to server DBFs)
RDO/ADO to pass the cursor.

WHERE IS THERE A SIMPLE model (or example) of how to make this happen?
HOW is a server mounted DCOM DLL instanced from the client?

As Always
Terry