>>>When testing on my local test database, the Requery brings a trashed last row.
>>>
>>>Requery is returning 0. Could it be possible that at the time Requery is being executede, the TableUpdate is about to finish its job and that is why the last row gets garbage in it?
>>>
>>>Has somebody else faced this situation?
>>>
>>>Any workarounds are appreciated.
>>>
>>>Regards and thanks in advance.
>>>
>>>Oscar
>>
>>This is pretty wierd. What kind of network?
>
>It is a very simple NT 4.0 server with Widows NT workstation PC's sharing the server database. The problem happens when using any of both, the local database or the Network database.
>
>I just added code to test the local view to check for this trashed row. If found then I have to execute a TableRevert, (since the trashed row dirties the local view) and then again the requery which brings back de required data in perfect conditions.
>
>Something I forgot to mention is that this is a parameter view, so it only retrieves a subset from its back table.
>
>Oscar

Have you tried putting something like a INKEY to case a pause between the TABLEUPDATE and the REQUERY? Not that I think you should have to do this, but it would certainly determine if the problem was timing based. The reason I doubt this, is that TABLEUPDATE has to wait until the updating SQL is finished before it returns .T., because it has to know that the operation was performed successfully...