Jim,
First things first. Very nice add-in.
![Smile :) :)](/styles/default/custom/smilies/smile.gif)
Interesting coding style you
have there.
What I realized was that I was assuming a great many things, well, one in
particular. When I create add-ins I make them temporary. This behavior is
described by you, in that you exit the Excel Application and "Cancel out"
the add-in is removed (barring correct coding of routine deletion/removal)
but the App remains. Your add-in has the temporary status as False (as
opposed to mine being True). This means that in this same situation, your
add-in will not be removed. It also means that when the (Excel) Application
is loaded again after closure, the menu bar will already be there, even
though it shows being loading.
I don't know if I really see an advantage to having the add-in temporary
status set to False. But then again I can't say I really see a strong
advantage to having it set to True as well.
Anyway, needless to say in all my testing that was the last thing I would
have thought of and it had me going for a while too! And apparently there
is not a lot of difference between the Addin_Install/Uninstall and the
Workbook_Open/BeforeClose event; besides what you have pointed out, which
can be a pain to the user. So I'll have to say that I would go with the
Addin events rather than the Workbook events for the add-ins. (Guess
somebody with common sense is saying, "Doh!" about now..) I actually had to
step away from this test completely and have my friend look at MY add-in
(last place I was going to start looking) to tell me what I had
wrong/different in my testing scenario. It was a learning experience. So
for that, thank you very much!!
![Big Grin :D :D](/styles/default/custom/smilies/grin.gif)