Trust access to Visual Basic Project

This policy setting controls whether automation clients such as Microsoft Visual Studio 2005 Tools for the Microsoft Office System (VSTO) can access the Visual Basic for Applications project system in the specified applications. VSTO projects require access to the Visual Basic for Applications project system in Excel 2007, PowerPoint 2007, and Word 2007, even though the projects do not use Visual Basic for Applications. Design-time support of controls in both Visual Basic and C# projects depends on the Visual Basic for Applications project system in Word and Excel.

If you enable this policy setting, VSTO and other automation clients can access the Visual Basic for Applications project system in the specified applications. Users will not be able to change this behavior through the "Trust access to the VBA project object model" user interface option under the Macro Settings section of the Trust Center.

If you disable this policy setting, VSTO does not have programmatic access to VBA projects. In addition, the "Trust access to the VBA project object model" check box is cleared and users cannot change it. Note: Disabling this policy setting prevents VSTO projects from interacting properly with the VBA project system in the selected application.

If you do not configure this policy setting, automation clients do not have programmatic access to VBA projects. Users can enable this by selecting the "Trust access to the VBA project object model" in the "Macro Settings" section of the Trust Center. However, doing so allows macros in any documents the user opens to access the core Visual Basic objects, methods, and properties, which represents a potential security hazard.

Supported on: At least Windows Vista
Registry HiveHKEY_CURRENT_USER
Registry PathSoftware\Policies\Microsoft\Office\12.0\PowerPoint\Security
Value NameAccessVBOM
Value TypeREG_DWORD
Enabled Value1
Disabled Value0

ppt12.admx

Administrative Templates (Computers)

Administrative Templates (Users)