...but if the machine is not logged in or gets rebooted, the tasks will not
execute.
The service is the way to go if this is more mission critical, the EXE +
scheduled task is it's not as critical. Considering the requirements for
this project, I'd go service.
Michael
> A console application scheduled using windows task scheduler to run every 5
> minutes is easier to implement and won't take take memory when it is not
[quoted text clipped - 18 lines]
> > >>
> > >> thank you
Sherif ElMetainy - 27 Jan 2005 16:32 GMT
The Windows Task Scheduler Runs as a Service, executes the commands even if
no interactive user is logged on.
> ...but if the machine is not logged in or gets rebooted, the tasks will not
> execute.
[quoted text clipped - 29 lines]
> > > >>
> > > >> thank you