Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.worksheet.functions
|
|||
|
|||
What may cause macro modules to be created by accident?
I've seen numerous posts here about how to resolve nagging macro
warnings in workbooks where the user claims there are no macros. I understand how to erradicate them. However, I'm curious as to what this group believes are the reasons as to why these modules are created in the first place. I saw in one post, someone suggested it could happen after right clicking on a spreadsheet tab and selecting "view code" by accident. Yet, if I try that, no modules are created, so I can't see how that would be the culprit. Another explanation would be if someone went so far as to begin recording a macro by accident and then promptly bailing out, and yes, I can see how that would generate a module. But it seems many foks feel these macros can appear without these types of activities. Are there any other actions that might cause unwanted modules to appear...things to caution users about during training? Thanks in advance for your input. |
#2
Posted to microsoft.public.excel.worksheet.functions
|
|||
|
|||
What may cause macro modules to be created by accident?
If you have the option to force declarations of variables turned on, then
rightclicking on a worksheet tab and selecting view code could cause "option explicit" to be added to the worksheet module--not a general module. That's enough to cause the warning the next time the workbook is opened. herrdue wrote: I've seen numerous posts here about how to resolve nagging macro warnings in workbooks where the user claims there are no macros. I understand how to erradicate them. However, I'm curious as to what this group believes are the reasons as to why these modules are created in the first place. I saw in one post, someone suggested it could happen after right clicking on a spreadsheet tab and selecting "view code" by accident. Yet, if I try that, no modules are created, so I can't see how that would be the culprit. Another explanation would be if someone went so far as to begin recording a macro by accident and then promptly bailing out, and yes, I can see how that would generate a module. But it seems many foks feel these macros can appear without these types of activities. Are there any other actions that might cause unwanted modules to appear...things to caution users about during training? Thanks in advance for your input. -- Dave Peterson |
#3
Posted to microsoft.public.excel.worksheet.functions
|
|||
|
|||
What may cause macro modules to be created by accident?
On Jul 16, 11:22 am, Dave Peterson wrote:
If you have the option to force declarations of variables turned on, then rightclicking on a worksheet tab and selecting view code could cause "option explicit" to be added to the worksheet module--not a general module. That's enough to cause the warning the next time the workbook is opened. Thanks Dave! I appreciate your time to reply with a great answer. |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
[GROUP] by accident, how to get rid of it??? | Excel Discussion (Misc queries) | |||
spreadsheet locked by accident | New Users to Excel | |||
Macro to import modules into a worksheet | Excel Discussion (Misc queries) | |||
How do I recover document replaced by accident? | Excel Discussion (Misc queries) | |||
Yikes - I overwrote a file by accident - is there anyway to get i. | Excel Discussion (Misc queries) |