Hi,
I'm sure there's probably an easy explanation for this, but I don't know what it is, and I can't seem to find an answer...
My workbook has several VBA modules in it. After it crashed while calculating, none of the buttons that referenced the modules worked. Excel no longer references the original macro names (for example, "macroname"). Now, it lists the active macros as "macroname.macroname." When I make calls from one module to another, all of the references are now messed up.
I can work around this recognizing the problem and reassigning the macros to macroname.macroname instead of just macroname. Same with the references. However, to avoid having to do this again in the future, is there a straightforward explanation as to what's going on? Is there a way to "reset" Excel's macro name recognition back to what the modules are actually called (they're listed correctly in the VBA Project window).
Any help is appreciated.
I'm sure there's probably an easy explanation for this, but I don't know what it is, and I can't seem to find an answer...
My workbook has several VBA modules in it. After it crashed while calculating, none of the buttons that referenced the modules worked. Excel no longer references the original macro names (for example, "macroname"). Now, it lists the active macros as "macroname.macroname." When I make calls from one module to another, all of the references are now messed up.
I can work around this recognizing the problem and reassigning the macros to macroname.macroname instead of just macroname. Same with the references. However, to avoid having to do this again in the future, is there a straightforward explanation as to what's going on? Is there a way to "reset" Excel's macro name recognition back to what the modules are actually called (they're listed correctly in the VBA Project window).
Any help is appreciated.
