I'm creating a Task Scheduler to use with our progress .p's and I'm using the RUN VALUE(SchTask.RunStatement). and if the .p was changed or "broken" and is returning an error, it stops the task scheduler all together, I've managed to keep it running with a :
DOLOOP:
DO ON STOP UNDO, LEAVE DOLOOP:
But its still producing the error from the other procedure. Of course the NO-ERROR option wouldn't work I'm now down to trying OCX'x that suppress messages but they have only worked on Windows messages not progress. This will be running persistanly on an administrator account which isn't manned by anyone so I can't have it returning any messages. I know this has to be a common problem but I can't seem to find the answer anywhere. Thanks in advance.
DOLOOP:
DO ON STOP UNDO, LEAVE DOLOOP:
But its still producing the error from the other procedure. Of course the NO-ERROR option wouldn't work I'm now down to trying OCX'x that suppress messages but they have only worked on Windows messages not progress. This will be running persistanly on an administrator account which isn't manned by anyone so I can't have it returning any messages. I know this has to be a common problem but I can't seem to find the answer anywhere. Thanks in advance.