Multiple timers accessing single class

Doug Aliff

We have third party software that has 20 MS Access database. The software resides on two boxes: 1 production and 1 for fail over.
I'm creating an app the copies the databases at different intervals; some monthly, some daily, and some every 30 sec. I plan to use a single class (CopyDB) to handle the copying. My question is since I have three timers running how do I ensure that I do not get a race condition or that I do not miss one of the copies (monthly, daily) because the class was being used to copy (every 30 sec). Will synclock be sufficient?

Thanks in advance for you suggestions

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

jacob smith15y ago
thanks for sharing information

How to write a resume | free resume templates
Rolando17y ago
Hi, For me synlock is not a very good solution when combined with timers, recently I was searching with a similar problem with timers and accessing to a shared resource, and the best answer I found was to stop the timer each time I begin the process, and restart it when I'm sure the process has been finished. In this way I'm sure that only 1 timer event is accessing the resource.