Cannot run the macro 'XYZ.xlam!Macro'.The macro may ....

[JurajM]

Hi All,

I'm trying to run VBA code in .xlsx, when .xlam in AddIns was created. However I'm getting this message, when I try to run it:

Cannot run the macro 'XYZ.xlam!Macro'.The macro may not be available in this workbook or all macros may be disabled.

If I create a module in .xlsx file and paste VBA code into module it runs smoothly.

Any ideas, how this can be fixed?

Thank you in advance.

 

[RoryA]

Welcome to the forum.

Are you sure the add-in is loaded and that the macro name is correct?

 

[JurajM]

Hi Rory,

Thank you for reply. Yes, real name is BC.xlam and was loaded ( ticked ) in Add-Ins.

So I still do not have idea, why this happening.

Any other ideas?

 

[RoryA]

What is the name of the macro and of the module it is in?

 

[JurajM]

macro name is Sub BC() and I didn't change module name so it is Module 1.

 

[RoryA]

That should be fine then. Can you explain exactly what you mean by this:

I'm trying to run VBA code in .xlsx, when .xlam in AddIns was created.

An xlsx is not a macro enabled file, so I'm not sure exactly what you are doing.

 

[JurajM]

I'm trying to run macro via Add-Ins as starting file is actually report ( usually excel format files which are not supporting macro, but that's why BC.xlam was created as than it shouldn't matter ), from where I'm doing selection from.
If I'm trying to go via Add-Ins it will give me this message:
Cannot run the macro 'BC.xlam!Macro'.The macro may not be available in this workbook or all macros may be disabled.

And only If, I create module in report .xlsx file and paste VBA code, it runs smoothly.

I was trying to save report file as .xlsm, if there will be any change, but unfortunately same message:
Cannot run the macro 'BC.xlam!Macro'.The macro may not be available in this workbook or all macros may be disabled.

 

[RoryA]

What exactly are you doing to try to run the macro? Clicking a button somewhere?

 

[JurajM]

Thank you Rory for your time. It was actually caused by macro name. The code was looking for the macro titled "macro', so that's why it didn't work.