Using multiple timers question

[rede96]

I have a form that triggers every 500ms, using the OnTimer event. The code that executes basically communicates with an external device, retrieves some data, which is then written to a table for logging.

I am creating a second form that I wish to trigger every 5 minutes to query the data written to the first table, write the results to a second table, which I will then use to create a graph in the second form. The graph will be visible at all times and update using the OnTimer event in the second form.

I will probably have up to 4 ‘pairs’ of forms running.

Is it better to use separate timer events in each form to control my project or should I just have one timer event to control the lot?

 

[KenHigg]

Something tells me you should have one timer event control the entire lot - Could get messy trying to debug with all those timers firing...

 

[rede96]

Something tells me you should have one timer event control the entire lot - Could get messy trying to debug with all those timers firing...

Yeah, you are probably right. Although once one 'pair' of forms was debugged, it's only a case of changing a few lines of code and some variable names to create others.

The most important thing for me is that each external device gets scanned every 500ms, the rest isn't too time critical.

When multiple timer events are being triggered, does access deal with them sequentially or can they overlap? The reason for asking is I didn't know whether or not to treat each pair of forms as a single application and maybe look at creating them in VB6.

 

[KenHigg]

Not sure how it habdles it all. Seems you could come up with a method to test different set ups and see how it acts... Post back what you figure out, I'd like to know -