>Ok for me not to use transactions but how do you handle problems like this :
>
>- tableupdate(parenttable) returns .t.
>- tableupdate(childtable) returns .f. and the user decides to cancel because he doesn't get out (locked record, some ruleexpression return .f., etc ...)
>
>What do you do with the parenttable that got updated already ?
>The problem gets more complicated as more tables need to be update the same time : as soon as one update fails (for whatever reason) ...

I think Pascal has it right. Transactions ARE used to rollback a failed one-to-many save routine's multiple TABLEUPDATE()s. He's not starting the transaction when the user starts editing, he's starting the transaction when the user tries to save. Right, Pascal?

- Rich.