TimerEvent vs system resources

[cainemart]

I'm making an auto logout form that will use the timer event. I was wondering if it uses a lot of the systems resources. We have an old computer that is dedicated to one access application and it will use the form. Just trying to figure out just how bad this will slow everything else down.

Is there an API call or something that might not be as bad on the sysmtem resources?

Thanks

TCM

 

[thornmastr]

Access is a resource pig. It always has been. It probably always will be. If you have resources, extra memory, crank up Access and watch all that precious memory drop before your blinking eyes.

Anyway, to answer your question….the correct answer is NO. Don’t worry about it. For as resource intensive Access is, it is the most forgiving Pig MS has ever fostered on the development community. If another process needs resources, Access will give them up as soon as they’re needed.

Access really does not need much to run. Like any other MS product, the more it has, the happier it is,, but it will function reasonably well on precious little; so use that form. Access is very forgiving of other processes.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[tedsmith]

Its a good idea to have only one timer control in your whole application.
If you want different simultaneous time delays, count down a variable every time the timer fires.
if you want different delays, use the same timer but vary the time delay in code and a flag that signals which delay is which (If Flag=1 then do timer 1 etc)