Palisade Knowledge Base

Knowledge Books

• Knowledge Books
• Standalone Licenses
• Network Guide
• More on Networks
• End User Setup
• Techniques and Tips
• Troubleshooting
• Licencias individuales
• Guía para Administradores de Red
• Licencias de red
• Configuración de usuario final
• Técnicas y Consejos
• Soluciones
• Licenças Standalone
• Licenças de Rede
• Configuração do usuário final
• Técnicas e Dicas
• Soluções
• Obsolete Articles

• Main Support Page

Home → Troubleshooting → All Products: Startup → "This workbook has lost its VBA project."

2.86. "This workbook has lost its VBA project."

When I try to launch my Palisade software, I get a pop-up like this one

Repairs to 'Risk.xla'

Excel was able to open the file by repairing or removing the unreadable content.

This workbook has lost its VBA project, ActiveX controls and any other programmability-related features.

You have Visual Basic for Applications disabled, either by a policy setting or because it was disabled during installation of Microsoft Office. Microsoft's articles Some Excel features are unavailable if you disable Visual Basic for Applications and run Excel and Considerations for disabling VBA in Office explain that this makes some Excel features unavailable, including some native Microsoft Excel add-ins and add-ins from third parties.

To solve the problem, re-enable Visual Basic for Applications:

1. Open Control Panel » Programs and Features (in Windows XP, Add or Remove programs).
2. Select Microsoft Office and click Change in the menu at the top, or right-click Microsoft Office and select Change.
3. Select Add or remove features and click Continue.
4. In the list that appears, click the plus sign to expand Office Shared Features.
5. Click the drop-down arrow next to Visual Basic for Applications and change it to Run from My Computer. Click Continue.

If VBA was already set to Run from My Computer, you or your IT department have set a system policy to disable it. This prevents many Excel features from working, as explained in the articles cited above. Please ask your IT department to remove the policy setting Disable VBA for Office applications.

That policy setting assigned a value of 1 to the VBAOFF value in the System Registry, according to Method 3 in How to turn off Visual Basic for Applications when you deploy Office, so you may be able to re-enable VBA by changing the value to 0. The VBAOFF value is located in HKEY_LOCAL_MACHINE\Software\WOW6432Node\Policies\Microsoft\Office\nn.0\Common or HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\nn.0\Common, where nn is 15 for Office 2013, 14 for Office 2010, 12 for Office 2007, or 11 for Office 2013.

Last edited: 2015-06-30