Re: Strategy to allow one user to drop another from the server

Kirk, We had a similar requirement. In our case it was users remaining logged on after they had gone home. We needed them to be kicked off in order to run maintenance and so the backup was not slowed. I used execute on client to display a dialog to the user informing them that they would be

Re: Strategy to allow one user to drop another from the server...

Execute on Client, of course!! Thanks Chip, Chuck, and Timothy! > On Mar 6, 2017, at 2:45 PM, Timothy Penner wrote: > > Calling QUIT 4D with EXECUTE ON CLIENT with a uniquely named/registered > client has already been mentioned (twice), that's probably what you need. > Here

RE: Strategy to allow one user to drop another from the server...

Calling QUIT 4D with EXECUTE ON CLIENT with a uniquely named/registered client has already been mentioned (twice), that's probably what you need. Here are some links to get you started: * REGISTER CLIENT: http://livedoc.4d.com/4Dv15.4/help/Command/en/page648.html * GET REGISTERED CLIENTS:

Re: Strategy to allow one user to drop another from the server...

On Mon, Mar 6, 2017 at 4:23 PM, rooftop99--- via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > 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

Re: Strategy to allow one user to drop another from the server...

execute on client (Quit 4d) getting it to right client might be the trick :) On Mon, 06 Mar 2017 13:23:11 -0800, rooftop99--- via 4D_Tech wrote: > 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