Hello John, I am generally relying on the standard built-in warning when opening a locked record that 4d does, but Locked By does return the locking process, user, machine, and proc name. And I am only seeing this so far on client-server. Thanks, Alan
On Wed, Dec 9, 2020 at 9:25 AM John DeSoi <de...@pgedit.com> wrote: > Are you using LOCKED BY to determine which user/process has the record > locked? In version 17 through 18R3 I have seen an intermittent bug where > Locked returns true but LOCKED BY indicates there is no lock. Only one > process uses the record, so it should not be locked. But I'm only seeing > this in single user mode, not client/server. > > John DeSoi, Ph.D. > > > > On Dec 8, 2020, at 3:32 PM, Alan Tilson via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > > > Well, going to read-only in the list view didn't change anything... > > But this doesn't happen on all or even most tables... > > Any ideas? > > ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************