You should always post your code but try inserting
on errror resume next
early in your code
--
Don Guillett
SalesAid Software

"Randy" wrote in message
...
I have a macro that was written long ago by someone no longer with the
company. The macro has workbook names hard coded in it that it opens from
a
share and reads one at a time. Everything runs great until the workbook
no
longer exists or the name has been changed. I'm a macro novice and am
wondering if there is a simple error routine that can be added which would
prompt me with the error and give me the option to continue on.
Currently,
it just errors out and I'm unable to generate critical reports until I
figure
out what's wrong.

Thanks in advance!

Randy