>in most cases I think the second would be better
>as ou can handle conflicts etc. for each record in turn
>
>Arnon
>
Hi Arnon,

Actually, we've just begun to use the second alternative today because we thought TABLEUPDATE with the first parameter set to "all records" should be the responsible for some implicit File Locks disturbing our multiuser environment.

Today, when we started with TABLEUPDATE with parameter set to "current record", I thought it would be a good idea to handle record locks manually before issuing the TABLEUPDATE command. But for my surprise, we frequently got an error which said something like "File lock not allowed within a transaction having prior Record Locks..." - which indicates that for some reason TABLEUPDATE even set to the current record uses File Lock.
Didn't understand...

Anyway, thanks for the suggestion, Arnon!

Renato