>This occurs when some users have problem when clicking on the mouse, bad connection, browser problems, etc. You would be surprise to see how many users are firing dual transactions by clicking in sequence on the same item.

interesting, got to remember that (bad users :-) )

>No, this is not the way it works. A first RLOCK() attempt is issued. If it works, it goes out immediately. If it doesn't work, the SET REPROCESS will determine the length before it reacts. Once it reacts, it will wait for a one millisecond INKEY. So, this can go 25 times. So, if SET REPROCESS is set to 5. It would go as a max of 2 minutes. We issue that approach for assigning primary keys. We do that several times per second. It works like a flash.

jup, you're right. i don't know wy i keep on messing up these logical expressions. got to get my eyes checked.