Automation of Access 2003 Jobs: Error Detection

We have a problem with the current setup. We have a couple hundred access databases that run overnight pulling information from SQL servers. If one of these access databases gets locked up (commonly something like SQL server timing out or a server share being unavailable temporarily), access doesn't reply with a recognizable exit code. The access program itself is fine, but the database processing or internal macro has halted with an error. At this point in time, I believe access and the database do no further processing.

What would be the best way to detect when these jobs error out and either closing and restarting them, or even just terminating the process?

This system was setup before I started working here and I don't see very in-depth usage so far, so I figured this may be the resource to tap.

Thanks.

If you know how long these jobs are expected to run you can set a timeout and have the job restart automatically in a hour or sooner.

A better approach is to make Access jobs to write to a log file and check for that log file presence of contents from 24x7 jobs. Further actions can be programmed depending on what is found in the log.