**SOME** Macros show up in the editor, but others do not

[jswhip]

Strange scenario.

1. Have an existing personal.xlsb file that I have used for many years.
2. Pre-existing macros show up in project view
3. New macros do NOT show up in project view
4. However, if I use the Developer tab --> Macros I can see the new macros
5. But I am unable to edit the new macros. Get a message stating "Cannot edit a macro on a hidden workbook..."

How do I get my new macros to show up in the editor?

Screen shots below (those highlighted in yellow don't show up in project view and can't be edited):

 

[Fluff]

NO macros show up in the project view you have shown, they are just modules.
You will need to look at each module to find the macros.

 

[jswhip]

NO macros show up in the project view you have shown, they are just modules.
You will need to look at each module to find the macros.

The modules contain macros within my personal.xlsb (unless I have my terminology incorrect). When I record a macro, it shows up as a module within personal.xlsb (or at least it used to) - e.g. Module 1, etc. I no longer see these new modules in personal.xlsb.

If I understand you correctly, the question is where are my missing modules?

 

[Fluff]

When you record a macro it does indeed create a new module. Have you checked in Module1 as that is the only standard module name.

 

[jswhip]

They were not in Module1. FWIW - if you record multiple macros, Excel creates new modules (e.g. Module1, Module2, etc)

My inelegant solution:
1. Insert a new module (aka "Module2")
2. Somehow was able to get into edit mode on one of the macros (not sure how, but there were 5 macros in the invisible module). See the 2nd print screen above for how I accessed the macro.
3. Copied and pasted all the macros into "Module2"

Other people in my department have been having VBA issues - the common thread is a Microsoft update that is getting rolled out incrementally. But it doesn't impact everyone with the update - the very same macro works for some people, partially works for others, and for others won't allow Excel to open (unless in safe mode).

I tried to record another macro and now I get "Cannot run Visual Basic macro because of a syntax error." There is something woefully off in my MS Office 365 or Windows 11 install.

 

[MARK858]

if you record multiple macros, Excel creates new modules (e.g. Module1, Module2, etc)

Not always, the macro's below were recorded separately but are in the same module (Module2)