>>Hi,
>>
>>I started this thread with the intention of finding the best way of executing an application from the server.
>>
>>I decided on putting this application .exe into the Windows Schedule on the VM server (as suggested here). The customer IT agreed with this approach.
>>
>>I finished creating the application. Copied the .exe and the configuration file (.XML) to the folder on the server where the program should start. I then ran the program from the command prompt, as a test. It printed what it was supposed to print.
>>
>>What kind of other test(s) should I do on this application before I ask the IT to Schedule it?
>
>If you're not doing so already, I'd test under the user account that will be used when the task is scheduled.
>
>I think this was discussed before but if your task runs unattended you might want to have it log success or failure to a file and/or e-mail.
The IT person said he would set up the program in the Win schedule under his account. I don't have his credentials; so I can't.
As far as problems, I set up the program to save error messages, if occurred, into a log file. So, I will be checking the log file for a few weeks. Then, once I see it works without a glitch, I may or may not set up email.
The customer knows - expects - that a bunch of reports will be printed on Monday morning. So, if nothing is printed, they will let me know, I am sure.
"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