Lets see: The ISP looks like this: An NT (with all the stuff it needs to be an ISP) SQL 7 VFP (loaded and running) A VFP ADO COM (DLL or EXE) It has Error call backs, it's registered and waiting for a client CREATEOBJECTEX(), and connects to the server's SQL through the server's (the ISP's) ODBC. The Client Looks like this: The VFP exe logs into the ISP ( i haven't even considered how this really works), but bear with me. The VFP client CREATEOBJECTEX(..\server COM) The VFP client sends a Datasource request to the ISP ADO COM. The ISP ADO COM Connects to the proper ISP Database (the client sent a connection string) The ISP ADO COM Requests a data set (the client sent a stored procedure call or SQL select satement) The ADO COM builds a recordset The VFP client creates a local reference to the ISP ADO COM's recordset The VFP client (maybe disconnect from the COM, and) process the local recordset. Almost everything we hear about ADo and COM relates to servicing Active Doc or ASP. I have always wondered, when the project calls for it, "Why can't an ISP ADO COM service a VFP client?" Regarding the initail connect and authorization to the ISP, I guess that could be done through an OCX WinSock