>Hello,
>
We are using a full blown application with forms and a timer.
Runs without a problem.

The advantage is that whenever there is a problem, and error message or any other diallog showing up, you can run it as a normal application, or as a services in the destop session.


We have been using this approach for over 10 years running many clients 24/7 and very few problems show up.
It definate can be as solid as any other approach.

Walter,



>I am working on creating a program which will be used as a service.
>
>In a nutshell, the program will consist of one form with a timer on it. The timer will run 24/7 and call a procedure every # minutes. The procedure will connect to SQL Server and based on some table/rows values will send email(s).
>
>Mainly the form will have a textbox which will show the end user the timer interval. My goad is to run the form minimized so that it won't be seen on the server. And the user will be able to change the timer interval by changing the text box value.
>
>A question:
>
>Can a program used as a service have a Form? Would the use have to stop the service to bring up the form to make a change?
>
>TIA