A shame there doesn't appear to be a way round it. Thanks for the advice
though Jon.

"Jon Peltier" wrote:

I've never found a satisfactory way around this. I tend to insert calls to
the routine that creates the xlApp object in a lot of places, so the object
is assured of being around "most of the time". Then I also put a button that
explicitly recreates the object somewhere in the menu.

Generally this is less of a problem when my users are using the programs
than when I am, since they don't go messing about in the VB Editor, and they
don't go crashing lots of things. (My development environment is a mess.)

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"Adrian Johnson, CA" <Adrian Johnson, wrote in
message ...
I've been working on a similar procedure, and have used the method
suggested
by Chip below.

I created a class and include the declaration in that class:
'Public WithEvents xlapp As Application'

I then create an instance of that class when ThisWorkbook is opened - the
technique Chip outlines on his very useful website.

It all works fine, unless I click on the stop button in the VBA editor, or
something similar, which destroys the object set up to capture the
application events.

Is there anyway around this?

Thanks.

Adrian.