On Sep 19, 2017, at 2:00 PM, Alan Chan 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. But even in this situation, I think 4D should try to deal with this. Maybe they could add some code to 4D Server that runs periodically like a “Janitor” routine that checks the list of locked record — I’m sure 4D Server keeps a list of this somewhere internally — and if it finds a locked record that is not linked to a currently connected user, it unlocks it. That would fix this issue and not require a 4D Server restart. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 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:[email protected] **********************************************************************
