I should think SET REPROCESS TO AUTOMATIC would be preferable. This is equivalent to -1 but the user can ESCAPE the deadlock.
>I have set up SET REPROCESS TO 10 SECONDS in a large, multi-user (50+) application.
>
>If record contention between two users exist, SET REPROCESS seems to work fine, but if record contention exists between more than two users, it's as if SET REPROCESS is set to -1 (record lock persists indefinitely). There is an ON ERROR procedure in place, but it never fires.
>
>Your insights are always appreciated,
>
>Thomas Allan
- Whoever said that women are the weaker sex never tried to wrest the bedclothes off one in the middle of the night
- Worry is the interest you pay, in advance, for a loan that you may never need to take out.
