From 23ee7239a1201061a0674e506753de8c1d8cf4c9 Mon Sep 17 00:00:00 2001 From: sankarbha Date: Tue, 22 Mar 2016 16:19:28 +0530 Subject: [PATCH] Update Build.bas Includes comment to fix 'Path not found' exception at Build.exportVbaCode --- src/vbaDeveloper.xlam/Build.bas | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/vbaDeveloper.xlam/Build.bas b/src/vbaDeveloper.xlam/Build.bas index 807cd21..5f1dfb4 100644 --- a/src/vbaDeveloper.xlam/Build.bas +++ b/src/vbaDeveloper.xlam/Build.bas @@ -10,6 +10,8 @@ Attribute VB_Name = "Build" ' 5. Enable programatic access to VBA: ' File -> Options -> Trust Center, Trust Center Settings, -> Macros, ' tick the box: 'Enable programatic access to VBA' (In excel 2010: 'Trust access to the vba project object model') +' If you get 'path not found' exception in Excel 2013, include the following step: +' In 'Trust Center' settings, go to 'File Block Settings' and check 'open' and/or 'save' for 'Excel 2007 and later Macro-Enabled Workbooks and Templates'. ' 6. In VB Editor, press F4, then under Microsoft Excel Objects, select ThisWorkbook.Set the property 'IsAddin' to TRUE ' 7. In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src' ' 8. Close excel. Open excel with a new workbook, then open the just saved vbaDeveloper.xlam