[AccessD] How to Manage Maintenance Mode - Auto shutdown

We generally don't have polite automatic shutdowns, since our software
could run for hours waiting for someone to finish a task and enter the
data associated with it.  If we have something along those lines (or we
need to compact/repair the front end) we set normally up the code to run
when it can get an exclusive lock on the database.  That just means that
when it thinks it should do this, as when the user is closing down, it
checks to see whether it can.  The same checks will happen on any
machine, so the last one to close down wins the prize of running the
maintenance routines.   

What specific kinds of maintenance were you going to run?

Charlotte Foust


-----Original Message-----
From: Mark Breen [mailto:marklbreen at gmail.com] 
Sent: Wednesday, August 17, 2005 9:37 AM
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