Re: RE:Row Locking

Yes, this is good idea to reduce lockes, but it also raise another problem, that in case an application is terminated unexpectedly before it reset the record to 'none', the record is never released. :) If this is the only choose, we may need an additional field to record the datetime and a timeout process to collect there un-released resources. Ken. gallucci@executone.com wrote in message <883415917.612892679@dejanews.com>... > We implemented a >pseudo-locking scheme where an additional column was added to the table ( >in this case, master ), and the default value was 'none'. When a user >needed to update the table, or any of it's child records, the presence of >the string 'none' in this column was checked, then his/her network logon >ID was placed in the column. Users hitting this row during an update >would get a message saying 'Record in use by Jane Doe'