Hi!

Just read the article that I mentioned. This will make a lot of things for you clear. In particular, to transfer data from COM to client and vise versa you can use disconnected recordset, that is in fact just still the same recordset, but you assigned "NULL" to its ActiveConnection property and passed it back to client from COM object as a returning value. Then modified and passed back to COM object as a parameter of some data updating method. Disconnected recordset could be only client-side recordset (adUseClient option).

>Have you ever build AS with ADO and SQL Server by yourself ?

What you meant as "AS" - Automation Servers? AS is not a proper word for this, use "C O M object" instead".
Yes, I have experiense in building middle-tire COM objects for accessing/updating data on SQL Server using ADO. VB, VFP, ASP and all combinations of these.
So you can call me.

HTH.

>Vladik!
>
>I have a proble m with this delays. And I think it's because if commad object. And I cannot or don't know how, use recordset as client, so I would be able move back and forward. And when I try to debar a VFP class, like you suggested, it seems like holding this command object over the net to my client computer.
>
>Have you ever build AS with ADO and SQL Server by yourself ?
>If so, may be I can call you and ask some questions ?