I don't remember - although I will look through the messages on this thread - what is the alternative to running the program under a person's account. I go by what the IT told me he would do. And this is what he said he would do.
Also, if/when he leaves and the printing stops working, they (the department for which I do the work) will scream bloody murder because this weekly printouts are very important to them.
>It has been pointed out already, that it's a bad idea to run application under some person account. It will stop working when person leaves the componay for whatever reason
>
>>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
