Hi Jeff, FWIW. I had this once in one of the two sites running the same app. A few days after converting from v13 to v16. One user and his processes were still visible in the 4D admin window and there were two records (from different tables) locked. The user was out of the office. No way out. Processes could not be killed, user could not be disconnected. The only solution was to shutdown and restart 4D Server.
I don’t know what happened. Probably the user did not log off correctly, but nevertheless having to shut down 4D Server is kinda drastical. One should be able to disconnect a user at any time and thus free the locked records. HTH Koen > On Mon, Sep 18, 2017 at 10:10 AM, Jeffrey Kain via 4D_Tech < > [email protected] <mailto:[email protected]>> wrote: > >> Has anyone who uses v16 run across false record locks being reported? -------------------- Compass bvba Koen Van Hooreweghe Kloosterstraat 65 9910 Knesselare Belgium tel +32 495 511.653 ********************************************************************** 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] **********************************************************************
