Hi, In a large client/server install we are implementing a function to allow one user (client) to drop another from the server. It seems that regardless of how much training is given, inevitably someone during the day walks away from their computer (lunch, etc.) with a record opened. Managers of the department who need access to the locked record attempt to contact the offending person. If they can’t they call the development team to drop the user from the server. I would like to cut out the middleman - me…grin.
I am just curious how others are handling this…? I have two possible strategies in mind: - Run a monitoring loop on each client that will test a flag. If flag is true, quit 4D. (Easy, but adds another resource pull on the server/client.) - Have 4D execute a command line statement to kill the app on the offending machine. (Fairly easy) Any thoughts? I am hoping I overlooked something and someone will say - “4D already has this function, just call xyz command..." Thanks, Kirk P.S. This is an all Windows based 4D installation... ********************************************************************** 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] **********************************************************************
