macros deleted but code still present.

[HP RodNuclear]

Sorry guys if my title was misleading but I had this spreadsheet that had many macros a predecessor of mine made that started when the workbook was opened. However, it had been awhile since the macro was used and when I went to open the spreadsheet again, the macro names were all gone but the code was still present! How did this happen and more importantly, how do I get my macro names back and get the code to work?

[jeffreybrown]

Not sure this makes sense, at least for me. If the macros are still present then the names are still present. Where do you expect to see these names that they aren't?

[HP RodNuclear]

Well, when you go to Tools -> Macros, the macros name are not present for us to even run but when I alt + f11, the code is all still there. Tried to call the important macros at the end with no success.

Please Login or Register  to view this content.

[HP RodNuclear]

It is alot of code but the two important pieces are the emergent code and the refreshdates code and I tried to call them at the end with no success. It gave me the debug error at the Call Emergent part. What is going on?

[johnjohns]

Tools->macros will show only those given in a module

[royUK]

The Workbook_Open code that you have posted is not viewable in the Macros list, it's event code & is automatically run when the workbook is opened with macros enabled.

If the rest of the code is in that module then that will not show either, it needs to be in a Standard module

[Colin Legg]

The "other" subs won't ever show in the macro list because they have parameters. ie.

Please Login or Register  to view this content.

The only one that will show is this one:

Please Login or Register  to view this content.

The Workbook_Open() handler won't show because it has been given a Private scope.


Edit:
Also, you will get an error if you run the SuperMacro() because it calls Emergent and RefreshDates without passing the required arguments:

Please Login or Register  to view this content.

If these procedures all used to be visible and SuperMacro used to run without a problem, I would suggest that someone has been tinkering with the code (adding in parameters).

[HP RodNuclear]

I think I resolved the issue. I don't know what exactly changed but I just made the private workbook open function a public function and sort of resolved the issue from there. Thanks for all you guys help and I actually learned quite a bit just from you guys explanations and my own tinkering as well. As always you guys rock!

-HP RodNuclear

[royUK]

You shouldn't change the Open_Workbook, what you need to do is move the rest of the code to a Standard Module