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