Hi Garry
THAT is a well argued reply, for which thank you
I will consider it well

I've considered the wholesale export/import procedure also
Nice to get confirmation this is what you need to fix a case properly

- bit busy right now
spilly
- and I see you've posted on my other thread too (pleased grin)

"GS" wrote in message ...
spilly39 presented the following explanation :
And anyway, my question still stands:
-Is there a bug in Excel around this issue?
-What is going on?
If we understand we can produce better products with less pain

As I stated in my previous reply, I had similar problems. In an effort
to resolve it I discovered there's a condition refered to as 'workbook
corruption' which I initially thought was similar to 'file corruption',
but eventually discovered I was wrong about that association. Fact is,
a corrupt workbook can have many different symptoms; the _Open event
being one place where those symptoms can manifest.

Since you state that you use Rob Bovey's CodeCleaner, you might find it
interesting that Rob is who educated me on the subject of workbook
corruption, and recommended I use the Auto_Open/Auto_Close method in
place of putting code in ThisWorkbook. To complete the transition away
from that class Rob also educated me on the concept of handling
Application events via a class module. This means I have complete
substitution for ThisWorkbook in all my projects.

Also, according to Rob the CodeCleaner utility won't fix workbook
corruption. The remedy he suggested to me was to export all the code
components with CodeCleaner and import them into a new workbook, and
close/delete the old file before saving the new one with the same name.
Not sure why the latter was necessary but I've never had Rob steer me
wrong in the 7 years I've known him.

--
Garry

Free usenet access at http://www.eternal-september.org
ClassicVB Users Regroup! comp.lang.basic.visual.misc