> At the server there is no such thing as "edit mode", only whether an
> uncommitted update has been performed. So it is still up to the user
> to have committed or rolled back the changes - and how that operates
> depends on how you have setup the client app.
>

O.K Let me write the sequence,

One Master table with some data
One detail table for storing debts and credits ( one to many
relationship )
One detail table for storing sums ( one to one relationship)

The Client started to add records to detail table.
After he finishes his work , the program starts ( This could be a SP or
Trigger or a code ) to update the sum table;

Try to lock the sum table (pessimistic )
if lock is successful then
update the sums
post
else
go into a loop
wait a while
try again to lock
if lock is successful
update the sums
post
exit
end of loop

what are the disadvantages of this process?

Metin Gonen