[AccessD] shutting down

True, you have to figure out some reasonable compromise on the length of the
timer interval. The KB article suggests setting the timer to fine every 1
second, but I find I get decent results when I fire it off every 30 seconds.
Then I set the actual idle time at 60 minutes.

So every 30 seconds the active form and control and control are checked.
After doing that 120 times, if the form and control have still not changed
it's a pretty good bet the user is not doing anything.

I also use the same timer event to check every minute to see if a flag value
in a table has been set. If it has all users are given 60 seconds to
complete what they are doing before everyone gets kicked out.

HTH

Lambert
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Monday, December 17, 2007 11: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.