Jim,

J> It is less trouble for us to write and maintain a single scheduler than
J> for a Windows user to hunt down, install, learn, and configure a third
J> party cron. I, for own, have written an internal database task schedule
J> but have yet to figure how cron work on Windows.

I don't think it's a very valid argument. Windows has had a built-in
scheduling tool in NT-based builds for ten years now. I don't even
know of third party products that do it and I have certainly never
known anyone that thought he needed one, because the built-in tool
works so well.

Lately I have been having exactly the same dilemma for an application
of mine: use the system scheduler or roll my own? Once all the pros
and cons of the two alternatives were written down, the system
scheduler won hands down. This rules out plain Windows 98 but that's a
favour I do to my customers, not a disservice.

Ciao
--
Nando Dessena