[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.