Trapping Errors Via Automation   

Is there a way to trap an error generated in another app that is controlled 
via automation? I have an Access 2000 app that opens Word 2000 and proceeds 
to open a series of documents and, in each document, parse the contents and 
write it to an Access table (the Access app, after opening Word, runs a 
macro within Word which parses and writes to the Access app via DAO).

Occasionally we get an error from Word (such as "document is locked for 
editing" or other), which hangs the process. The process is an overnight 
one, so, obviously, if it hangs from a Word error message.

Is there a way to trap these error messages generated by Word and just move 
onto the next document?

Thanks,

Neil

date: Sun, 08 May 2005 03:18:31 GMT   author:   Neil