[AccessD] shutting down

I saw that at first as well.  However, this is a 60 second timer, with
presumably a 30 or 60 minute 'inactivity time'.  This means that the system
will only begin to shut down when the same control on the same form has had
the focus 30 or 60 times in a row.  This seems like a valid test of
inactivity.

If this is coupled with some type of 5 minute visual warning to the user, it
will work well.  It's better than setting up a timer for every form in the
database.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Monday, December 17, 2007 10:01 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] shutting down

>
> The goal is to detect inactivity on the part of the user. The example
> provided by M$ does just that by checking if the active form has not 
> changed
> in the defined time and that the active control on whatever form has not
> changed either. There's not much else you can do. If a user is interacting
> with a database then one or other of those objects is going to be changing
> frequently. So a timer event kicking off every few seconds or so fits the
> bill quite well.

=======The problem I have with the solution is that the control could've 
changed -- just because it's the same control doesn't mean that the user has

chosen several and returned to that control. Now, I might understand how the

code works, is that the case?

Susan H. 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com