Is there a way to influence Obj-Browse with nolock?
With Obj-Browse and MSSQL, if we are to open lots of records, I think it will put READ-COMMIT on the records. If we have 10K records by default, would this cause the deadlock if another thread is updating one of the records which has READ-COMMIT on it by Obj-Browse?
Is there a way to put nolock?
Message was edited by: Marissa Rogers - added category