I appreciate the input, but a lot of the suggestions just don't apply. I'll go ahead and elaborate, so if you get bored reading I'll understand.
This is a real simple test app consisting of a form which has two grids bound to two tables, a couple text boxes for (domain) username and password, and the timer. Sure, there are a couple labels scattered around too, but there is no user interaction with the form at all. It just sits there on a spare monitor a does its thing.
All the form does is fire the timer event every 1000 milliseconds which checks to see if 5 minutes has elapsed. If so, the code queries a server for certain process names/IDs to see if CPU usage has changed. If it has, those processes show as green in the grid's DynamicBackgroundColor. Otherwise, they show as red, letting me know they may have stopped.
At first, I thought maybe setting the interval to 0 when the 5 minutes expired, running the code, then resetting it back to 1000 at the end of code execution may cause grief. But the timer has been stopping anywhere but at the 5 minute mark. It could be at 1:27, 2:35, 4:43, anytime.
I left it running when I went home last night, and when I got to work this morning, the 'Last Checked' caption read 20:13, and the 'Time Remaining' caption read 2:27 and was stopped.
By the way, I have my workstation power save sleep mode set to 'Never', so I know that's not an issue.
Ali,
I did delete the timer and add a new one after your suggestion, so I'll see how that behaves.
In the meantime, this isn't a critical production app, more of an experiment. But there is a good chance that future timer based apps currently in use at our office will be moved to W7 or W8 machines. I would like to I'm not going to have problems with those. Or at least be able to find a workaround.
Anyway, thanks again for the suggestions!
-Dave Summers-
![[cheers] [cheers] [cheers]](/data/assets/smilies/cheers.gif)
Even more Fox stuff at: