>You are using the VFP 3.0 syntax for TableUpdate. IN 3.0 TableUpdate took three arguments, 1st T/F all records/current record, 2nd T/F force update/fail on conflict, 3rd (often ommitted) is the alias to be updated.

That explains. I didn't pay attention to this change when we moved to VFP 5.

>VFP 5.0 has a newer syntax for this function which takes 4 arguments;
>
> 1st 0,1,2 (old T/F work also) 0 means update current record
> 1 means update all records and fail
> immediately on any record failing
> 2 means update all records and fail only those
> with a problem
>
> 2nd T/F Force past conflict, fail on conflict

That seems to be close to VFP 3 syntax. The second parameter is still T/F. BTW, the help does not mention anything about this syntax.

In our case, in the Save() method, we applies all the lock before saving then we do TableUpdate() on each table. By having all locked before TableUpdate(), we didn't have any problem until now as it was alwasy working. Have you ever had the situation where, even if all is locked, TableUpdate() was failing?

In our case, we don't use the Begin Transaction, End Transaction and Rollback as we need to support free tables. In the situation, TableUpdate() is failing, what kind of mecanism can we do to revert all changes?