The SQL Server lock manager really doesn't have a means to implement pessimistic locking. Plus there's an issue that the optimizer decided the granularity of the locks based on the query that is running.

You could simulate it by implementing a semaphore lock. Create a column and write a value to it when someone wants to edit the record. Remove the value when the editing is complete or aborted.

-Mike