See:
http://www.sql-server-performance.com/reducing_locks_hints.aspI think, IMHO, that it is better to use a flag and a timestamp. The flag indicates the lock state, and the time is the lock time. Then you could have a SQL job that runs and checks the lock times and automatically unlocks records that are past expiration.
>Amilcar,
>So there's not "locking" mechanism inherent within SQL Server?
>Yau
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
