>Amilcar,
>So there's not "locking" mechanism inherent within SQL Server?
>Yau

No! In the SQL server "world" the word "record" does not even exist, everything is "set based", meaning that if you want to refer to a "record", you must specify this "record" by some specific value. This specific value may be field values, like "where cust_no=100" or it may be PK related, like "where PK='123456123'. This specific value must be unique if you want call only one "record". The PK solution, where the PK value itself is automatically generated and has absolutely no reference to the "record" as such, is the preferred solution, and according to many SQL gurus it's the only solution.