Well, I am absolutely certain it makes sense. I just am not certain that I understand it yet.
Let me see if I get it ... you added a custom button to a standard toolbar by using View >> Toolbars >> Customize, adding a button, then assigning a macro. Or something very similar to this. When you assigned the macro, the workbook (let's call it Book1.xls) was open and you assigned to the button "Macro1" (for example).
Now, when you press the button, it opens the Book1.xls and runs "Macro1".
In addition to this, that Book1.xls has a Workbook_Open Event procedure that calls "Macro1".
Well, this all makes perfect sense now.
OK, there are several things you can do. The easiest (if you are the only person using the workbook) is to kill the Workbook_Open procedure completely. You don't need it anymore. But, I assume you thought of that already and it's not what you want to do.
Something that is incredibly simple to do, but difficult to explain would be the following (just trust me on this, OK?) ...
In Book1.xls, in a Module (maybe the same one that contains Macro1), put this as the very first line in the Module (before "Sub Macro1", for example):
As the first 2 lines of code in Macro1, add this:
What this will do is make it so that Macro1 cannot run more than once per session.
Bookmarks