This question is worth 0 points because I have no points to give right now. If you are feeling charitable, by all means continue reading. I leave the decision to you.
I have an application I wrote that resides on a network drive. One big problem is whenever I want to update the .exe I have to wait until everyone has exited out of the program, because I can't replace the .exe when it is in use.
What I want to do is figure out a graceful way to exit the application, giving those who are actively using the program enough time to finish what they are doing and exit before the program dies.
I want to create the ability to "down" the program by some means. My thought right now is to set up a TTimer event that checks for the existence of a file every so often. Let's say the file is called KILLME.TXT. The code would look something like this:
procedure TFormMain.Timer1Timer(Sender: TObject);
Now, this method is not smart because other dialogs may be open at the time or the user may be in the middle of something.