>I have never seen this before, but I guess the first thing you have to do is to check SET REPROCESS setting (should be AUTOMATIC). If you still will see the problem, you can proceed by old RLOCK() way (have separate Locker table with particular record locked when a user try to perform specific operation).

I have SET REPROCESS TO 2 SECONDS. If I put AUTOMATIC, how will this change the behavior?

In my case, I have 2 collisions approx. per month when 2 applications insert a record. This is the insertion which is the most busy in the application. The error is always the same. It is also at the same line.