Why not just use the task scheduler that ships with Windows?


>Hi all
>I'm thinking about a 'scheduler' and request advice on best strategy.
>
>The scheduler will run a batch update process in VFP app at that workstation at intervals the user selects, e.g. every 4 hours. This interval could be stored in a table or the Registry.
>
>I'm not at all sure if this is a job for the VFP timer class, or something like the WSH or Task Scheduler. I am looking at Bela Bodec's cpptimer from the Files section. The process has to run inside the application - not suitable for a separate .exe. There may be Messageboxes or other processes which cause VFP timers to pause running at times in the app, but precision in the interval isn't very important, so those don't really matter. Most of my VFP timers are very short-lived affairs so far. I do have a central app class method available which can turn them all off and on again as required for certain other processes.
>
>I am considering VFP timers created in code from a custom class - one for the 'hour' hand with very long interval of 360000 and one for the 'minute' hand of the clock, interval 6000. The hour hand is always enabled, the minute hand is not. The next time due would be a property of the custom class, calculated from the interval stored in the Registry, and if the hour hand determined it fell in the next hour, it would start the minute hand ticking to fire the batch process when due.
>
>This might work but it could be a long time before the bugs it causes come to the surface - so, other ideas anyone?
>
>TIA
>
>Dick