Microsoft KB Archive/212716

= WD2000: Macros Not Listed After Creating New Document in Windows Explorer =

Article ID: 212716

Article Last Modified on 10/11/2006

-

APPLIES TO


 * Microsoft Word 2000 Standard Edition

-



This article was previously published under Q212716





SYMPTOMS
When you use Windows Explorer to create a new document based on a Word document that contains macros, the macros do not appear in the macro name list, even though they are still stored in the document. (To locate the macro name list, on the Tools menu, point to Macro, and then click Macros.)

NOTE: If you have macro virus protection turned on and you click the Disable Macros button in the warning dialog box, your macros are disabled and they will not appear in the macro name list.

To create a new document from an existing document in Windows Explorer, right-click the file and click New on the shortcut menu that appears.



CAUSE
The macro storage components that contain the list of macros are not copied to the new document.



WORKAROUND
To view the list of macros, use either of the following methods:

Method 1: Create a Copy of the Document Using Word
Create a copy of the document using Word instead of Windows Explorer.
 * 1) Start Word.
 * 2) Open the original document.
 * 3) On the File menu, click Save As.
 * 4) Select the folder you want to save the file in, type a file name for the new document, and then click OK.

Method 2: Create a New Macro in the New Document to Rebuild the Macro Table
If you used Explorer to create the document, create a macro in the new document. This rebuilds the macro table that contains the list of macros stored in the document.
 * 1) On the Tools menu, point to Macro, and then click Macros.
 * 2) In the Macro name box, type a name, such as Test, and then click Create.

If you are prompted to replace an existing macro, click No and type a new name.
 * 1) On the File menu, click Close and Return to Microsoft Word.

NOTE: You do not need to type any commands into the macro.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

