Standard locking question
Posted on 1998-06-23
Okay, I know this must have been asked a 1000 times on this page. But here it is anyway.
I have multiple processes that will be accessing the same MS SQL table. Their first access will be to see what the next unique id (dbint) is so it can be assigned to their record. I have the logic working for a single access point. But I am worried that when multiple accesses occur, each one might get the next id in order (1, 2, 3, 4...the next one would be 5) and think it is theirs. How do I prevent multiple accesses to the same table from thinking they should get the next unique id?