VBA Module Name

[328mike]

I changed the Module names for a few of my macros in VBA and now their shortcuts wont work in Excel and I can't create any shortcut. What is the problem here?

 

[Leith Ross]

Hello 328Mike,

Changing a module name does not affect the macro's procedure name. The shortcut only cares about the procedure name so something else must be going on.

You say you can not create a shortcut. Do this apply only to the previous macros or to new ones as well? Are you assigning the shortcut using VBA code or manually with the macro dialog? Which modules names did you change?

Sincerely,
Leith Ross

 

[328mike]

Hello 328Mike,

Changing a module name does not affect the macro's procedure name. The shortcut only cares about the procedure name so something else must be going on.

You say you can not create a shortcut. Do this apply only to the previous macros or to new ones as well? Are you assigning the shortcut using VBA code or manually with the macro dialog? Which modules names did you change?

Sincerely,
Leith Ross

Module names were Module 1 Module 2 Module 3...etc.

I changed them to reflect the macros they contained.

This is what happened to the macro text in the macro menu list after doing that:

PERSONAL.XLSB!CGMFormattingWIRELINE.CGMFormattingWIRELINE

it doubled the name for all of them. The shortcuts I have assigned and any new shortcuts I assign won't work.

 

[Leith Ross]

Hello 328Mike,

It looks like you gave your module the same name as the macro. If you did then that is the problem. This will confuse the VBA compiler. I will use underscores in my module names (spaces are not allowed) so I know what the macro is but not confuse VBA.

For example, I would name the module CGM_Formatting_WIRELINE and the macro name would be CGMFormattingWIRELINE. Change the name, resave the file, and you should be okay.

Sincerely,
Leith Ross

 

[328mike]

Thanks so much Leith Ross.

 

[nawazmehdi]

Hello 328Mike,

It looks like you gave your module the same name as the macro. If you did then that is the problem. This will confuse the VBA compiler. I will use underscores in my module names (spaces are not allowed) so I know what the macro is but not confuse VBA.

For example, I would name the module CGM_Formatting_WIRELINE and the macro name would be CGMFormattingWIRELINE. Change the name, resave the file, and you should be okay.

Sincerely,
Leith Ross

Thanks a ton!!