Article ID: 282830 - View products that this article applies to.
This article was previously published under Q282830
Code that is written to automate an Office application and programmatically manipulate the Microsoft Visual Basic for Applications (VBA) environment and object model may fail on Office with one of the following error messages:
From Visual Basic or VBA:
From Microsoft Visual C++, Microsoft Foundation Classes (MFC), or ActiveX Template Library (ATL):
Run-time error '6068': Programmatic Access to Visual Basic Project is not trusted
The same code works without error on computers with Office 97 and Office 2000.
HRESULT = 0x800A17B4 (-2146822220) "Programmatic Access to Visual Basic Project is not trusted"
Office adds a security option to deliberately lock out programmatic access to the VBA object model from any Automation client unless a user chooses to permit such access. This is a per user and per application setting, and denies access by default.
This security option makes it more difficult for unauthorized programs to build "self-replicating" code that can harm end-user systems.
For any Automation client to be able to access the VBA object model programmatically, the user running the code must explicitly grant access. To turn on access, the user must follow these steps.
Office 2003 and Office XP
Article ID: 282830 - Last Review: October 6, 2011 - Revision: 6.0