Hi,
My boss wants me to lock a record in SQL Server 7 when a select query is done (we don't have a special edit mode - user can change the record and it will be written when he moves to another record).
Since this is not really "normal", it's "normal" to lock when you write, not read, I was wondering what you're thinking of that (and besides, it's impossible to lock 1 record while reading without using extra fields (lock-boolean).
Since he pays me I continue searching for another way to lock then using the extra field, but I'm not really happy with this... why would someone want to lock when reading anyway?
Gimme your opinions... (hehe and some good arguments to change the mind of my boss... :-))
Happy coding ;-)

Crazy D @ Work :-)