[AccessD] shutting down

When you think about it, this is not really the kind of thing that a single
API could handle. 

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.

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 10:12 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] shutting down


Yeah, I've seen that one too. I was hoping for something a little more 
succinct -- like an API or something, but I haven't found anything.

Thanks!
Susan H.


> Hidden form. Timer even on said form. Check the current control and
> current
> form in the event. See here for all the details...
> http://support.microsoft.com/kb/210297

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