[AccessD] (Don't) Force Closing the FE

Yes it does.  

In  frmInactiveShutDown
Private Sub Form_Timer()
'**********************************************************************
'* This timer event procedure will shut down the application
'* after a specified number of minutes of inactivity. Inactivity
'* is measured based on how long a control remains the ActiveControl.
'**********************************************************************

And it doesn't allow remote control or shut down at a specific time.

Very limited compared to previous posted solutions.

-- 
Stuart

On 21 Feb 2011 at 9:58, Doug Murphy wrote:

> Jennifer,
> 
> I just ran across the following utility for shutting down an inactive
> Access application. Does not us a form timer.
> http://www.peterssoftware.com/isd.htm. I have not used this so can not
> comment on functionality, but it does look promising.
> 
> Doug 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer
> Gross Sent: Monday, February 14, 2011 2:49 PM To: 'Access Developers
> discussion and problem solving' Subject: Re: [AccessD] (Don't) Force
> Closing the FE
> 
> Hi Robert and Gustav,
> 
> I have to get all users out of the database at the end of day in order
> to do maintenance or make data structure changes to an evolving
> database.  I am open to any suggestions including learning more
> sophisticated coding than I am used to . . . 
> 
> I don't have any long running processes that would take more than a
> minute or two, so checking for inactivity every 30 minutes, with shut
> down after 60 minutes idle is reasonable for what I am working on now.
> 
> Jennifer
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav
> Brock Sent: Monday, February 14, 2011 2:41 PM To:
> accessd at databaseadvisors.com Subject: Re: [AccessD] (Don't) Force
> Closing the FE
> 
> Hi Robert et al
> 
> I can confirm this observation. 
> It just doesn't work reliably and can cause serious trouble for data
> consistency unless you somehow - while any important function runs  -
> inhibits the timer, which may imply coding on a higher level than you
> are used to - using classes, WithEvents or the like.
> 
> /gustav
> 
> 
> >>> robert at servicexp.com 14-02-2011 23:09 >>>
> The only problem with a "timer" solution is that in heavily used /
> complicated databases, running a timer can cause some very unexpected
> result with other code procedures. For some reason Access (at least
> with the programs I use to build (large complex)) has never liked
> timers, internal (form) or external (API).. I think it has something
> to do with running them in the same thread Access uses.
> 
> I had to use network commands inside of access (ActiveX) to shut a
> user down.  Not automatic, but very effective (and more complicated)
> 
> WBR
> Robert
> 
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jennifer
> Gross Sent: Monday, February 14, 2011 4:53 PM To: 'Access Developers
> discussion and problem solving' Subject: Re: [AccessD] Force Closing
> the FE
> 
> Beautiful.  I knew this had to be a problem that others had faced in
> the past.  Was always able to get around it because of my network
> permissions - with this database I can't do that.
> 
> Appreciate all your help - including the idea of an entry/exit log -
> that's a great one.
> 
> Jennifer
> 
> 
> --
> 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
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>