[AccessD] Form Timer Alternitive

Robert,

<<The only thing I do know for sure is, I simply cannot have a form timer
running inside of the same mdb.>>

  I don't understand why not.  The solutions you suggested are no different
in terms of the end result.

  I have a hidden form I open at the startup of my apps and use for a bunch
of purposes, one of which is firing off a timer to support background tasks.

  The only "tweak" is that I have a flag to turn it off to aid debugging.

Jim Dettman


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Robert Gracie
Sent: Tuesday, December 28, 2004 10:09 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Form Timer Alternitive



 Hello All,
 Has anyone come up with an alternative to using a form timer? I have great
need now to come up with a solution for monitoring inactivity. Access form
timers, used in a complex program, seems to reek havoc, and creates a wide
variety of anomalies.

 So I need to come up with an alternative. Does anyone know if these
possible solution would work?

 Solution 1
Create a form timer class in a referenced MDE that will raise events that I
can grab in the front .mdb. What I'm not sure is if the timer class code can
monitor activity in the .mdb. The other question is if this form timer is
going to cause the same anomalies.

 Solution 2
Using the same basic idea as above, but with a completely separate mde
(un-referenced) to monitor activity in the mdb in question.

 Solution 3
Using Windows API's (Have no clue about this one) for the timer &
monitoring.


The only thing I do know for sure is, I simply cannot have a form timer
running inside of the same mdb.

Any idea's?

Robert Gracie

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