Macro that won't go away!
 

I have a user that has created a macro for a particular spreadsheet that she
uses. After deciding she no longer needed the macro, she removed it from the
source document and saved the changes. However, attempts at re-opening the
file after removing the macro prompt the user to constantly enable/disable
macros, though there is no macro in the work, and the source document did not
do this before the macro was created and introduced.

Macro that won't go away!
 

Could you elaborate further on VBE? Thanks!

"Toppers" wrote:

In VBE (Alt+F11) , remove any "Modules" as they will invoke the message even
if there is no code.

"Michael Stroud" wrote:

I have a user that has created a macro for a particular spreadsheet that she
uses. After deciding she no longer needed the macro, she removed it from the
source document and saved the changes. However, attempts at re-opening the
file after removing the macro prompt the user to constantly enable/disable
macros, though there is no macro in the work, and the source document did not
do this before the macro was created and introduced.

Macro that won't go away!
 

VBE - Visual Basic Editor.

Press Alt+F11 keys and you will get the VBE. On window on left-hand side
you will references to workbooks open which include the one causing you
problem (assuming it is open!).

Delete any "Modules" which apper in the w/book (usually called "Module
1","Module 2" etc. Right click on the module(s) and select "Remove
module...". Don't save before deleting.

If problem still persists, right click on each tab in the w/book, "View
code" and delete any code you find.

HtH

"Michael Stroud" wrote:

Could you elaborate further on VBE? Thanks!

"Toppers" wrote:

In VBE (Alt+F11) , remove any "Modules" as they will invoke the message even
if there is no code.

"Michael Stroud" wrote:

I have a user that has created a macro for a particular spreadsheet that she
uses. After deciding she no longer needed the macro, she removed it from the
source document and saved the changes. However, attempts at re-opening the
file after removing the macro prompt the user to constantly enable/disable
macros, though there is no macro in the work, and the source document did not
do this before the macro was created and introduced.