Article ID: 317405 - View products that this article applies to.
This article was previously published under Q317405
In Microsoft Office 2000, automation is considered a "trusted state", and, therefore, macros in a file are turned on by default, regardless of the security setting. The Application.AutomationSecurity property allows Microsoft Office XP programs to support security for solutions that programmatically open a document but are uncertain whether the macros in a document are safe. A developer may want to have the Office XP solution display the security warnings to the user for these documents.
To use the Application.AutomationSecurity property on a computer that has Office XP installed, you must install Microsoft Office XP Service Pack 2 or a later version.
For additional information about the latest service pack for Microsoft Office XP, click the following article number to view the article in the Microsoft Knowledge Base:
307841Note Microsoft Office 2003 does not require any updates to use the Application.AutomationSecurity property.
(http://support.microsoft.com/kb/307841/ )How to obtain the latest Office XP service pack
AutomationSecurity propertyThe Application object of Microsoft Word, Microsoft Excel, and Microsoft PowerPoint supports this property.
This property returns or sets an MsoAutomationSecurity constant that represents the security mode that an Office XP program uses when programmatically opening files. This property is automatically set to msoAutomationSecurityLow when the program is started. Therefore, to avoid breaking solutions that rely on the default setting, be careful to reset this property to msoAutomationSecurityLow after you open a file programmatically. Also, be sure to set this property immediately before and after you open a file programmatically, to avoid malicious subversion.
This property also allows macros to choose to open a document and to trigger the appropriate security warning, which is the same as if an end user is manually opening the document. This new property does not affect the behavior when the end user uses the user interface (UI) to open files. In this case, this property does not change the settings in the Security dialog box (on the Tools menu, point to Macro, and then click Security).
The following are the MsoAutomationSecurity constants that you can choose from:
The value of the DisplayAlerts property does not apply to security warnings. For example, if the user sets the DisplayAlerts property equal to False and the AutomationSecurity property to msoAutomationSecurityByUI while the user is on the Medium security level, security warnings appear while the macro is running. This action allows the macro to trap "file open" errors, while still displaying the security warning if the "file open" succeeds.
Article ID: 317405 - Last Review: April 9, 2007 - Revision: 3.2