Custom form without code causes macro warning (289147)


The information in this article applies to:

  • Microsoft Outlook 2002
This article was previously published under Q289147

SYMPTOMS

You receive the "Enable/Disable" macro virus warning when opening an item, but the form does not contain Visual Basic Scripting Edition (VBScript) code.

CAUSE

The item at one point contained code or some text in the Outlook Script Editor. If the text was later removed, the item is still marked as having code.

WORKAROUND

To work around this problem, publish the form in one of the forms libraries, such as the Organizational Forms Library, the Personal Forms Library, or the Folder Forms Library. When you publish the form in one of the forms libraries, Outlook considers the form safe, and the macro warning does not appear.

For additional information about the workaround, click the following article number to view the article in the Microsoft Knowledge Base:

290663 Outlook does not run VBScript code when you open an item

STATUS

This is a limitation of Outlook custom forms.

MORE INFORMATION

For additional information about why you receive the security warning when you open an item, click the following article number to view the article in the Microsoft Knowledge Base:

290663 Outlook does not run VBScript code when you open an item

REFERENCES

For additional information about available resources and answersto commonly asked questions about Microsoft Outlook solutions, click the following article number to view the article in the Microsoft Knowledge Base:

287530 Questions about custom forms and Outlook solutions

Modification Type:MinorLast Reviewed:3/9/2005
Keywords:kbprb kbSCRAPKeep KB289147
©2004 Microsoft Corporation. All rights reserved.