>>>>But the timer has to "live" somewhere and to me a form is just as good place for it as any :) And I understand that once the application starts (maybe after server reboots) it runs unattended. Simply connects to the SQL Server every # minutes and - based on some logic - emails or does nothing.
>>>
>>>If you go the console app route, you set up Windows Task Scheduler to run it every n minutes.
>>>In essence, Task Scheduler provides your timer.
>>
>>Yes, I understand. I actually have an application which is all reside in one .PRG file. And this .EXE is fired by my ASP.NET application. It works very well. So, I will base this program on the same .PRG approach.
>
>It is a good approach.
>The other thing I like about running a console exe from the task scheduler, is that I can run it in windows or in a dos box for debugging.
>Console messages let me see how it is running.
>If it goes by too quick, I can read the log file.
This is exactly right. this is how I test/troubleshoot my .EXE based on one .PRG.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham