I normally use 'doevents' in a loop to have a program wait for a specified trigger but judging by the program's CPU usage while it's waiting, this isn't the best way to go.
I need to have a program trigger and record text on a webpage every 1/2 hour. I've thought about using Windows Scheduled TAsks to do this, but the lowest time denomination you can repeatedly run a program is once daily.
It'd be nice to have the program open and left that way while it waits every 1/2 hour to record text on the webpage without using as many CPUs as 'doevents' does. Any suggestions?