Waiting on lock.....

[reasegurator]

In our TurboImage database the rollback doesn't work as well as in RDB 
and VMS so if something wrong happends during the update this is a 
good way to control and revise if the records are ok and investigate 
the reasons of the problem. (our users usually don't phone us when a 
error happends and with this, they are forced to do it).
Also, if you have a field in the lock master where you can save the 
signonuser of the one who is locking... you can also find a guilty ;-)

Anyway, a not controlled error during the update procedure it's not 
very common. If you are making controls in the preupdate, you set the 
flag to 1 at the end of the procedure, after all the validations.

For example, I work in an insurance company and the Spanish law said 
that the claims must be numbered consecutively and without gaps 
between numbers. If the rollback doesn´t work, this is the best way to 
set the counters to the correct number. Without this you can't realise 
if you have a gap untill it's too late.

Dani

Senior Programmer