Dan Waters
dwaters at usinternet.com
Wed Aug 17 14:37:13 CDT 2005
I've done this for several years and it works very well. The user gets a five-minute warning (fine in this app), their data is saved due to a 120 second refresh rate, and no complaints. This being a form timer in Access doesn't really matter. If it's 5 minutes +/- 30 seconds, users won't know or care. Also, my db will pop up a form on the admin's PC to let them know when everyone is logged out (and this is just a counted 7 minutes after the shutdown sequence). Dan Waters -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: Wednesday, August 17, 2005 12:18 PM To: 'Access Developers discussion and problem solving' Cc: 'Mark Breen' Subject: RE: [AccessD] How to Manage Maintenance Mode - Auto shutdown Go here to get the code to perform an automated shutdown. http://support.microsoft.com/default.aspx?scid=kb;en-us;304408 The code used is dependant on a form timer, and only looks for inactivity. But it is very simple to modify it to also check a flag value in a table periodically to see if the app. is being forced to close by the administrator. I use this method all the time. Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Breen Sent: Wednesday, August 17, 2005 12:37 PM To: accessd at databaseadvisors.com Subject: [AccessD] How to Manage Maintenance Mode - Auto shutdown Hello Group, I have an app uses MS SQL 2000 Server as it's backend database. I want to run some maintenance routines on the db and they require that I switch the db into single user mode. This is easily done and once I have it in Single User Mode, it is easy to kick off the maintenance routines. My question is what ways you may have handled a polite automatic shutdown of the application in your worlds. Technically, I do not have to shut down my app, I could just break the connection to SQL server, but I think that I may as well shut down the entire app. I could use timers, and I could insert 'activity' updates and only shut down the FE app when the app is not being used. So for example, I could update a database field and when the field has not been used for more than 30 minutes I can assume that it is in-active. This would allow me to auto shut down the app, but I would like to leave some message behind me to let the user know where their app went rather than just killing it! I could also break the connection to the db, then display a message box saying the db has been shutdown and allow the user to click OK to continue. I am not seeking detailed technical help here, more philosophically how you guys handle this type of situation. Any thoughts or comments are appreciated, I hope you and your family are all well, Mark Breen -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com