Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have two add-ins that create their own menus. In fact, I use Walkenbach's
MenuMaker to do this. This problem happens when they are both installed and loaded into memory. I have a sub-menu in both custom menus that have the same captions and same items, but refer to procedures only within the respective add-in; the add-ins do not reference each other at all. The problem is that when both menus exist, the submenuitems in both menus call the *same* procedure. SubmenuItem 1 in Menu A and SubmenuItem 1 in Menu B both call the procedure in Workbook A, even though the .OnAction property refers to the correct (separate) workbooks. I suspect that it has to do with the fact that the structure of the menu is the same, and/or the name of the procedure it calls is the same. But why does this happen? I have tried changing the procedure names in the workbooks so that they are not identical, and this fixes the problem.... but is there any other way around it? Any help would be most appreciated. |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
referring to previous worksheet in workbook | Excel Worksheet Functions | |||
Vlookup referring to External Workbook or Spreadsheet | Excel Worksheet Functions | |||
Formula referring to a dynamic range in a different workbook | Excel Worksheet Functions | |||
Referring to external workbook in Data Validation | Excel Discussion (Misc queries) | |||
Referring to function in another workbook | Excel Worksheet Functions |