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.
Alan Chan 4D iNug Technical <[email protected]> writes: >The client timeout will remove a dead user after that period of activity. In >these cases, the user isn't even showing in the list of connected users on the >server, yet 4D reports the lock in that user's name. > >It's pretty weird. I guess others have seen this before, but it's new to me. I >can understand a lock for a user that's still technically connected but >non-responsive (crashed, hanged, etc.) but not if the server isn't even >showing the user in the >list. > > ********************************************************************** 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] **********************************************************************
