Considering you have given a lot more detail here, I am not surprised. This is the first you have made mention of XML.

When you work with a disconnected recordset and you try to connect that recordset again in order to post data, the recordset must be created from a live connection. In your case, it looks like you are fabricating a recordset from XML. While you may be able to fabricate and open a recordset, being able to directly update a backend from that recordset is likely to be rejected by the server.

Why bother with the XML. If you need a recordset and you are attempting to update with a recordset, why not just stick with a recordset? What benefit do you get from XML?


>Thanks for reply.. but you not undertand me..
>
>Ok, this a example
>
>Client:
>
>Request for a list of areas
>
>Server
>
>Return the list in Ado-XML format
>
>Client
>
>Get the xml, convert it to recordset
>
>User:
>
>Editing the recordset (add, edit and delete records)
>
>Post data
>
>Cliente
>
>Convert recordset to XML, send to server
>
>Server;
>
>Convert again to recordset, connect to Sql Server 2000 and post
>
>AND!!!!!!!!!!!!!!
>
>Return generated Id IN ANOTHER XML!!!! (i need do it... in another way, i get crashes if use the same recordset beacuse is in multi-user, networked app. In a error VFP NOT FREE POINTERS (=objects ) so Bommmb!)
>
>Cliente
>
>THIS NOT WORK:
>
>Convert the XML id's into another recordset and assign new id to the news client recordset because the user need keeping editing . Imposible refresh! Too many records (somethings) and is very slow....
>
>I know that it is a bug from Microsoft... but not exist a workaround?
>Understand?