You could use the user's login ID as a lock flag. If the field is empty, then the record is unlocked. If it's not empty, then only the user who has locked it can unlock it from any station (or an admin).

The locking/unlocking should be done in one session on one station however. The scenario you mention could be used if the user's computer crash.

HTH

>How do I keep the current lock specific to a perticular user. Is there a unique connection # or something I could use so that only the one user that updates the field can reset the field even if the same user logs into SQL from another station with same id ?