>Problem:
>
>Some of the users of our applications (hospital Environment) never exit the application before they go home. Thus when their IS guy goes to review the backup that ran the during the night, there are 30-40 files that were open and did not get backed up.
>
>The IS guy have a newer, better, faster server on a full 100megbyte path that he wants to move our application to, but he won't do it till I give him a way to kill all the instances of our application that may be open before his backup runs in the middle of the night.
>
>Any help or pointers to tools for this would be greatly appreciated.
>
You could create an application timer that checks the system time and at a specified time, it could shut itself down. The good thing about the app closing itself is that it would know if changes were pending and it could exit gracefully while a thrid-party solution may cause data loss or index corruption.