>>>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.