>>>The Timer interval is not specified in minutes, but in miliseconds. Just calculate the next time minus the current time (in seconds), and multiply by 1000, to set the appropriate .Interval.
>>>
>>>>I'm building a timeclock buzzer application. At certain times during the day buzzer.wav plays. So I need to figure out how to fire off these events. The times I want buzzer.wav to play is something like...
>>>>
>>>>05:59
>>>>06:00
>>>>11:29
>>>>11:30
>>>>14:29
>>>>14:30
>>>>
>>>>
>>>>I can use a timer and compare the system time but I need the timer interval to be less than 1 minute (as you can see above) and that could cause the buzzer to play multiple times within that time slot. Any ideas?
>>
>>This sound inaccurate. Seems like it could wander using this method. That's why I figured if every 10 seconds I could look and see if my machine time (atomic time) was 05:59 I would play the wav. Your method leaves me at the mercy of the internal clock tick correct?
>
>You mean you have an internal clock ticker that needs very often updates from atomic clock? Then it'd be almost all the time out off synch with atomic clock. I'd then first buy a more trustable HW.
>Cetin

This method basically removes the atomic clock from the system. I check the time once, then forever (or till a system crash or restart) depend on calculating the time based on whatever drives the timer ticks.