CCS Point of Sale
You are here: start » office » transaction_management » trouble_shooting
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
office:transaction_management:trouble_shooting [2009/03/05 04:15] markphsd created |
office:transaction_management:trouble_shooting [2018/12/23 12:11] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Trouble Shooting Word Templates ====== | ||
| + | |||
| There are few options in Microsoft that may prevent operation of the word file: | There are few options in Microsoft that may prevent operation of the word file: | ||
| Line 4: | Line 6: | ||
| 2. If you have to re-reference the Setup: | 2. If you have to re-reference the Setup: | ||
| + | |||
| Programmatic access to Office VBA project is denied | Programmatic access to Office VBA project is denied | ||
| View products that this article applies to. | View products that this article applies to. | ||
| Line 17: | Line 20: | ||
| Office 2007 | Office 2007 | ||
| SYMPTOMS | SYMPTOMS | ||
| + | |||
| 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: | 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 Visual Basic or VBA: | ||
| + | |||
| Run-time error '6068': Programmatic Access to Visual Basic Project is not trusted | Run-time error '6068': Programmatic Access to Visual Basic Project is not trusted | ||
| + | |||
| From Microsoft Visual C++, Microsoft Foundation Classes (MFC), or ActiveX Template Library (ATL): | From Microsoft Visual C++, Microsoft Foundation Classes (MFC), or ActiveX Template Library (ATL): | ||
| + | |||
| HRESULT = 0x800A17B4 (-2146822220) "Programmatic Access to Visual Basic Project is not trusted" | HRESULT = 0x800A17B4 (-2146822220) "Programmatic Access to Visual Basic Project is not trusted" | ||
| The same code works without error on computers with Office 97 and Office 2000. | The same code works without error on computers with Office 97 and Office 2000. | ||
| - | Back to the top | + | ===== CAUSE ===== |
| - | CAUSE | + | |
| 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. | 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. | This security option makes it more difficult for unauthorized programs to build "self-replicating" code that can harm end-user systems. | ||
| - | Back to the top | + | ===== RESOLUTION ===== |
| - | RESOLUTION | + | |
| 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. | 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. | ||
| - | Back to the top | ||
| - | Office 2003 and Office XP | ||
| - | 1. Open the Office 2003 or Office XP application in question. On the Tools menu, click Macro, and then click Security to open the Macro Security dialog box. | ||
| - | 2. On the Trusted Sources tab, click to select the Trust access to Visual Basic Project check box to turn on access. | ||
| - | 3. Click OK to apply the setting. You may need to restart the application for the code to run properly if you automate from a Component Object Model (COM) add-in or template. | ||
| - | Back to the top | + | ===== Office 2003 and Office XP ===== |
| - | Office 2007 | + | |
| - | 1. Open the 2007 Microsoft Office system application in question. Click the Microsoft Office button, and then click Application Options. | + | 1.Open the Office 2003 or Office XP application in question. On the Tools menu, click Macro, and then click Security to open the Macro Security dialog box. |
| - | 2. Click the Trust Center tab, and then click Trust Center Settings. | + | 2.On the Trusted Sources tab, click to select the Trust access to Visual Basic Project check box to turn on access. |
| - | 3. Click the Macro Settings tab, click to select the Trust access to the VBA project object model check box, and then click OK. | + | 3.Click OK to apply the setting. You may need to restart the application for the code to run properly if you automate from a Component Object Model (COM) add-in or template. |
| - | 4. Click OK. | + | |
| + | ===== Office 2007 ===== | ||
| + | |||
| + | 1.Open the 2007 Microsoft Office system application in question. Click the Microsoft Office button, and then click Application Options. | ||
| + | 2.Click the Trust Center tab, and then click Trust Center Settings. | ||
| + | 3.Click the Macro Settings tab, click to select the Trust access to the VBA project object model check box, and then click OK. | ||
| + | 4.Click OK. | ||
Trace:
