Hi,

Thanks for this.

Yes compile errors should be picked up in the first place when creating
and testing the macro - should have realised that.

I got it wrong in that I was wanting the intercept and replace a
"runtime" error message when a user does something that I have not
thought of or tested for.

Example of the error message:-

"Microsoft Visual Basic
Run time error ###########
Automation error
The error invoked has been disconnected from its clients"

Also exited completely out of Excel - stating reporting error

Can this message be replaced with my own message as stated previously.

Cheers,
Bernz


--
BernzG
------------------------------------------------------------------------
BernzG's Profile: http://www.excelforum.com/member.php...o&userid=22949
View this thread: http://www.excelforum.com/showthread...hreadid=388193