>PMFJI < I've been following this avidly ... lurking, I guess ... and trying to understand it all > I *think* that what Craig is saying is not "that you can't _directly_ write to a VFP table", but that a COM object that lives on the server can not write to a VFP table on the client (user) computer. So a COM object on the server side "talks" to a COM object that lives on the client's side (?).
>
>< waiting to be pounced upon and corrected! >
>
POUNCE!!!!
There objects cannot be connected. Remember that we are stateless and in order for a COM object on the server to communicate with a COM object on the client, you would require a stateful application. What I was saying was that the COM object on the server will talk to the ASP page and pass back an ADO record set. Once the HTML has been sent, the COM object on the server goes away. A new COM object is created on the client via java, javascript or vbscript. This object was written in VFP and the ADO recordset is passed to it as a parameter and the table is then updated.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer