>>>Hello,
>>>
>>>A couple of times I received email error message pointing to the fact that
>>>'ShellExecute.prg' does not exist.
>>>
>>>In my code I do have calls to execute the ShellExecute (Windows API function) when printing PDF documents.
>>>So, the ShellExecute is outside of what my program created.
>>>
>>>What would cause this error?
>>
>>Admin, who forbade your exe to shell out? I've seen similar stuff in some environments when, in windows scheduled tasks, the user under whose credentials the task was supposed to run, suddenly lost that right.
>
>It could be it. Although strange thing is that sometimes it works, other times it does not. I think that if Admin forbade the exe to shell out, it would stop running this (shellExcute) all the time.
>I just asked the user who sent me the error email this morning to reboot her PC. I will see if the problem will be fixed.
>I am also thinking that I should enclose this call into Try Catch and avoid the user having to see this error.
>Thank you.

I looked at the code and see that the call to ShellExecutre is already enclosed in Try Catch. And yet, the error occurred and the customer sees the error.