Record Locking

[Richard Kreiss]

I would say that auto or @entsrl in most likely running on each record during a browse. 

As for record lock during reports I usually add a -u to the output command line. This allows *report to run on all records selected. The only time I don’t use a -u for an kutput is for an accounting output where a record change can cause issues. 

Richard Kreiss
Sent from my iPhone

> On Apr 12, 2021, at 8:46 PM, Jose Lerebours via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> What do you attribute your record locking issues most often to
> 
> A. Two or more users trying to update the same record
> B. Running a report while a user is in update mode
> C. Rebuilding indexes  while user is in update mode
> D. User closed connection leaving a lock file behind
> E. Lookup processing that locks but does not release record
> 
> To me, (B) was the most common record lock instances till I decided to run reports ignoring this and just keep on moving.
> 
> I rarely ever heard of two users trying to update the same record - I do remember seeing situation where a user will use the arrow up/down and
> reach a record where a user was sitting in update mode and the "waiting for record to be unlocked ..." came up; even without any processing being triggered.
> 
> Do not hold me to "even without any processing being triggered" part of the above statement but I am at least 80% sure of it.
> 
> What about you?  What would be your most frequent reason?
> 
> 
> -- 
> 
> Jose Lerebours
> 954 559 7186
> 
> https://www.asisuites.com
> https://www.helpsuites.com
> https://www.cargosaas.com
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list