Mark Breen
marklbreen at gmail.com
Wed Aug 31 03:53:12 CDT 2005
Hello All, Thanks for your replies on this thread, you gave me what I was looking for - some opinions. I have not worked on it yet, but I did notice that yesterday, the app had not been used since midnight and I was looking at it at 10:00 am, so an element of Johns auto logout will probably be required, in conjunction with an activity monitor, as this app is used for production support, it is not possible to request a logout. The timer and auto logout are OK, but what I have to contend with is the user attempting to log back in, this will have to be handled elegantly, or as an Indian guy I worked with recently says "I will have to fine a graceful solution to this" I thought the graceful was slight out of context for day to day language, but I thought it wonderfully apt. Thanks again for all your time, I always appreciate it. Mark On 8/17/05, Mark Breen <marklbreen at gmail.com> wrote: > > 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 >