|
|
Out of curiosity, I reran the macro recorder. This time, it provided a different macro for the statement that erred out. It now uses the FILE.IMPORT instead of the RUN command.
It has not failed since I changed the macro. It had been failing intermittently.
Let's just close this out. If it reoccurs using the new command, I'll reopen a ticket.
Thanks for the quick reply and support
John Sikora
|