Requery is appropriate when you have an open connection to the database. With MTS being a stateless environment you don't have a connection that persists all the way to the client. What you would do is refresh the recordset from the backend if you need to by re-issuing the query. This is somewhat of a "manual" Requery since all that it does is a Close and Open on the recordset.

There are other approaches to this, one being keeping a local copy of the data that is discarded after the current user process is done. Any other requests for data are satisfied from the backend.

In any case, the source for a disconnected recordset should be kept. How are you retrieving the rs from the client and what code is used on the MTS object that hits the backend?

>Hi,
>
>Another problem with VFP & MTS...
>
>(I "correct" the problem with arrays passing the ado recordset like XML and join each recordset in a 1 string separate with '^' char... great?.. Ah, and is not possible return -back multi-returning recordset...)
>
> I simply need call requery when the recordset is updated. Outside MTS is not problem, but inside, i get the recordset with the property Source(= The Sql string), so sending it no can do requery becuase Source is empty.
>
>Ok, a STUPID solution is return back the sql string, and send it again when i need do requery (and chage AGAIN the code...)
>
>But, not exist a workaround? I fell that if other properties return empty...
>
>Thanks...