>Thanks to you both for responding.
>
>What I was probably incorrectly referring to was something similar to what Bill was describing. In my situation, multiple users are performing several operations each, when completed, record the fact that the operation was performed. I had been using INSERT INTO table (fields) VALUES( values ).
>
>Yesterday was a particularly heavy day and several users complained that the system was not repsonding and I saw that they had the WAIT WINDOW "Attempting to lock record..." showing. Others just had a process hung where that INSERT statement was executing.
>
>So I was trying to determine if my SET REPROCESS or other code was perhaps improper.
>
>I would think that with SET REPROCESS TO AUTOMATIC, once one user left the table, the next would get it and so forth. But it apparently did not happen that way.
>
>Again, thanks for the input.
>
>Dave
>

Would be good to use table buffering with TABLEUPDATE() so you can check for collisions and retry, notify user, and recover, etc.

Bill