Hi Marco,

I don't often see a dutch member here on the UT.

Next to the SET REPROCESS approach, it could be helpfull to determine if some programs which operates on the large table is using implicit or explicit file-locking. When some program is using a REPLACE ALL FOR .... command which needs some time to complete it could leed to some serious concurrency problems. (e.g. File is in use by another in other programs). If you could determine the programs which are using this implicit file locking maybe you could rewrite them into recordlocking programs.

replace the REPLACE ALL FOR ... commands with SCAN FOR .... REPLACE ... ENDSCAN to avoid file-locking.

Though the REPLACE command is one of the most common implicit file locking command, the're a lot more commands that use implicit file locking.
DELETE ...
RECALL ...
UPDATE ...
APPEND FROM

etc