"Document contains macros" message when there are none

[Laura]

In both Word 2002 and 2003 I've been receiving the security message "This document contains macros, enable/disable" when I open certain documents.

However, using the VBE there are no macros in the document. I've scanned the documents for viruses and found none.

These are documents that had macros ON them, but not put IN them. I had put a document variable in these documents, but even after deleting that (which I don't consider a macro), when I try opening the documents, I still get the security warning.

Has anyone else had this happen? Any ideas?

(I don't know whether I should be highly irritated or concerned.) I certainly don't want others getting macro warnings when they try to open my documents.

Thanks so much.

 

[Jezebel]

Word considers that the document has macros if it has VBE modules, even if
those modules are empty. You need to remove the modules completely.

Don't understand the distinction between a document with macros 'on it'
rather than 'in it'.





In both Word 2002 and 2003 I've been receiving the security message "This
document contains macros, enable/disable" when I open certain documents.

However, using the VBE there are no macros in the document. I've scanned
the documents for viruses and found none.

These are documents that had macros ON them, but not put IN them. I had put
a document variable in these documents, but even after deleting that (which
I don't consider a macro), when I try opening the documents, I still get the
security warning.

Has anyone else had this happen? Any ideas?

(I don't know whether I should be highly irritated or concerned.) I
certainly don't want others getting macro warnings when they try to open my
documents.

Thanks so much.

 

[Laura]

Jezebel,

Thanks for your reply.

That's the thing -- there are no modules.

When I look at the document through the VBE project explorer, the only thing
beneath "Microsoft Word Object" is "ThisDocument." There is also a
reference to Normal.doc. But I see both of these for every document. There
are No Forms and No Modules.

What I meant when I said that I ran macros ON the document was that I used
macros (from a global template) to manipulate text in the document -- mostly
to create and apply list templates and styles. But they should not be
putting macros into the document -- and if they did, I'd think I could see
it through the VBE project explorer.

This has happened on about a dozen of my documents over the last 6 months.
I'm wondering if anyone else has experienced this and knows what causes it.

Many thanks.

 

[Laura]

That's the thing -- there are no modules.

When I look at the document through the VBE project explorer, the only thing
beneath "Microsoft Word Object" is "ThisDocument." There is also a
reference to Normal.doc. But I see both of these for every document. There
are No Forms and No Modules.

What I meant when I said that I ran macros ON the document was that I used
macros (from a global template) to manipulate text in the document -- mostly
to create and apply list templates and styles. But they should not be
putting macros into the document -- and if they did, I'd think I could see
it through the VBE project explorer.

This has happened on about a dozen of my documents over the last 6 months.
I'm wondering if anyone else has experienced this and knows what causes it.

Many thanks.

 

[Howard Kaikow]

Jezebel,

Thanks for your reply.

That's the thing -- there are no modules.

When I look at the document through the VBE project explorer, the only thing
beneath "Microsoft Word Object" is "ThisDocument." There is also a
reference to Normal.doc. But I see both of these for every document. There
are No Forms and No Modules.

What I meant when I said that I ran macros ON the document was that I used
macros (from a global template) to manipulate text in the document -- mostly
to create and apply list templates and styles. But they should not be
putting macros into the document -- and if they did, I'd think I could see
it through the VBE project explorer.

This has happened on about a dozen of my documents over the last 6 months.
I'm wondering if anyone else has experienced this and knows what causes

it.


There need not be any modules present.

If a template gets dirtied in certain ways, Word thinks there are macros.

This drove me nuts whilst developing
http://www.standards.com/index.html?SetVBAProjectPassword.