jwcolby
jwcolby at colbyconsulting.com
Fri Jan 27 10:56:37 CST 2012
I hear ya. However this is an app which runs reports, does imports etc. The things it does is scheduled by records in a table. I guess I could just put something in that table that shuts it down at a specific time. John W. Colby Colby Consulting Reality is what refuses to go away when you do not believe in it On 1/27/2012 9:03 AM, Jim Dettman wrote: > > You might also want to go this route: > > How to detect User Idle Time or Inactivity in Access 2000 > http://support.microsoft.com/kb/210297 > > or a combination of the two methods. > > But whatever you do, the app should close itself rather then being killed > from the outside, or you risk database corruption (unless of course it's a > SQL server backend, then kill away). > > Jim. > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Friday, January 27, 2012 08:06 AM > To: Access Developers discussion and problem solving > Subject: [AccessD] How to shut down Access > > The client wants to shut down Access for doing a backup. The backup kicks > off in the middle of the > night and they need a way to terminate the access application. I do not > have anything built in to > my stuff to do this. > > Does anyone know a way to directly get a pointer to any open access > instances and force them to close?