When an external process is started 24x7 can wait for the process to complete and then check the process exit code reported by the process. If your Access macro aborts but Access as a operation system process exits with the exit code 0 it is still indicates a successful run. To deal with such cases you can the following: In your Access macro you should write to some database table or a file some "flag" value that would indicate the process status as "started". If the macro completes as the last operation it should update the "flag" to some value that treat as a success. In 24x7 you run the Access file using a script with RunAndWait command and then you check the "flag" to find out the real job status. If the status is "success" you are ok, otherwise you perform some corrective actions. On the other hand, you can specify a timeout value for the job as a parameter in the RunAndWait. In case if your macro aborts with a message box, at some point the started process will timeout; 24x7 then will kill it and automatically treat the job it as failed. 24x7 supports a vast array of commands (called statements) that can be used to verify virtuall any type of "flag" as well as perform various process checks, including searches for messages boxes (WindowFind) and other. : How does a failure in a job stream get handled if the
: external job being run locks or aborts ? : example: Access can run macros on openning but can get
: caught if the macro tries to run an operation on a table
: that has been dropped. It will error out and stop, most times
: with some kind of message box that requires at least
: an ok button click.
|
