If they are supposed to be exiting filemaker application entirely, try Exit Application.
Thanks Phil. It seems a bit heavy handed since they might be using other databases of their own. Is there any other option?
That's why I qualified the suggestion with "if they are exiting filemaker all together...":smileywink:
The following script usually works for me, but not always:
Sometimes though file references between the files pop a file you've closed back open and it can be a bit like bopping gophers on a head until you figure out the best sequence in which to close the other files so that they stay closed.
Hi KS, all that needs to happen is go to a null layout (without any fields) before bringing your files in for a landing. This will prohibit the (automatic) reopening of any files due to their field being on the layout.
The solution is served? You can disconnect them after certain length of time - go to Server Admin for settings.
That leaves me wondering what's wrong with one of my files. That's exactly how I used to do this in 5.5, but the converted file insists on popping open a related file or two even though there is no reference to the file on the current layout. I'm probably missing something in the file's design. Definitely worth a second or third look...
Thanks. I was imagining something like this but missed the null layout. With that in place there will be no external data in use and I will close the files in an appropriate (data dependent) order.
As for the server timeout, I'll set that up as well. A good reminder...