How about placing an YIELD or may be a couple of them instead of WAIT. Does it help? : In regards to my previous post with the on error goto statement.
: We are having a problem with the OnErrorgoto statement working properly when
: it goes into the error routine. It
: BOMBS out on a CONCATEX statement. When I put a wait command just before the
: concat it works fine: Below is the trace log results with and without the
: WAIT : 125: Executing
: FILEOPEN("z:\aupft\tamtron\Automation\SearchFileTypes_Path.txt",
: "LineMode", "Read", "false", "0") : ERROR: "File not found"
: 397: GETLASTERROR : Return "File not found"
: 398: CONCATEX : At that point, the processing halts completely. : Here is the trace log for the same script, but with the Wait statement added. : 125: FILEOPEN
: 125: Executing
: FILEOPEN("z:\aupft\tamtron\Automation\SearchFileTypes_Path.txt",
: "LineMode", "Read", "false", "0") : ERROR: "File not found"
: 397: GETLASTERROR : Return "File not found"
: 398: WAIT
: 398: Executing WAIT("2")
: 399: CONCATEX
: 399: Executing CONCATEX("AUTOMATION ERROR Processing Notification -
: Charge Import (", "TEST CHARGE IMPORTS SCRIPT", ") -
: File "", "", """, "")
: 400: CHOOSECASE
: 400: Executing CHOOSECASE("job_progress",
: "END_CHOOSE_CASE_JOB_PROGRESS") : Why does the script need to be paused for script execution to continue?
: It is important that I am accountable for the reason the script needs the
: WAIT to process properly. The script will be performing a critical
: function. I must be able to account for any anomalies in the script
: processing to ensure I prevent them for occurring in other scripts and in
: this script at another location. : Thank you : ~Joe
|
