> On Sep 19, 2017, at 3:21 PM, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com> > wrote: > >> If a record wasn't unloaded in trigger properly, the record would be locked >> even after the invoking client user left the system (no longer signed in). >> The only way is to restart the server. > > This is a great point. I wonder if any of the users reporting this problem > have triggers that are doing some “fancy stuff” that could be causing this.
I still think there is a new bug in version 16, but I have not seen it happen again since upgrading to 16.2. This is a single user application with one process accessing the record. There is a trigger, but it just assigns one field and nothing else (no "fancy stuff"). John DeSoi, Ph.D. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
