I think you're going to have issues doing this no matter how you choose to "lock" the records, because if the user closes the web form while a record is locked, it is likely to leave that record locked until you have some process come along and remove the lock.
A better way might be to simply warn the user/block the save if the record changed during their edit session by comparing the values retrieved to that user originally with the same values retrieved from the row just before the save.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St