Skip to content

Commit 7ddd716

Browse files
meyeraxelhilkoc
authored andcommitted
Improved instructions for installation process
1 parent a36e551 commit 7ddd716

File tree

1 file changed

+15
-4
lines changed

1 file changed

+15
-4
lines changed

src/vbaDeveloper.xlam/Build.bas

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,28 @@ Attribute VB_Name = "Build"
99
' 3. Rename the project to 'vbaDeveloper'
1010
' 4. Enable programatic access to VBA:
1111
' File -> Options -> Trust Center, Trust Center Settings, -> Macros,
12-
' tick the box: 'Enable programatic access to VBA' (In excel 2010: 'Trust access to the vba project object model')
12+
' tick the box: 'Enable programatic access to VBA' (In excel 2010: 'Trust access to the vba project object model')
13+
' If you policy seetings don't allow to change this option you can create the following registry key:
14+
' [HKEY_CURRENT_USER\Software\Policies\Microsoft\office\{Excel-Version}\excel\security]
15+
' "accessvbom"=dword:00000001
1316
' If you get 'path not found' exception in Excel 2013, include the following step:
14-
' In 'Trust Center' settings, go to 'File Block Settings' and check 'open' and/or 'save'
17+
' In 'Trust Center' settings, go to 'File Block Settings' and un-check 'open' and/or 'save'
1518
' for 'Excel 2007 and later Macro-Enabled Workbooks and Templates'.
1619
' 5. If using a non-English version of Excel, rename your current workbook into ThisWorkbook (in VB Editor, press F4,
1720
' then under the local name for Microsoft Excel Objects, select the workbook. Set the property '(Name)' to ThisWorkbook)
18-
' 6. In VB Editor, press F4, then under Microsoft Excel Objects, select ThisWorkbook.Set the property 'IsAddin' to TRUE
21+
' 6. In VB Editor, press F4, then under Microsoft Excel Objects, select ThisWorkbook in vbaDeveloper. Set the property 'IsAddin' to TRUE
1922
' 7. In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'
2023
' 8. Close excel. Open excel with a new workbook, then open the just saved vbaDeveloper.xlam
2124
' 9. Let vbaDeveloper import its own code. Put the cursor in the function 'testImport' and press F5
22-
' 10.If necessary rename module 'Build1' to Build. Menu File-->Save vbaDeveloper.xlam
25+
' 10.Right click on 'vbaDeveloper', Import File for:
26+
' * CustomActions.cls
27+
' * EventListener.cls
28+
' * MyCustomActions.cls
29+
' 11.Read the instructions in ThisWorkbook in vbaDeveloper Project and uncomment the code if you want automatic import and export enabled
30+
' 12.If necessary rename module 'Build1' to Build. Menu File-->Save vbaDeveloper.xlam
31+
' 13.Open the Excel workbook where you want to use vbaDeveloper and add vbaDeveloper.xlam as reference to load the Add-In with the workbook:
32+
' In VB Editor -> Tools -> References -> Browse and select vbaDeveloper.xlam
33+
' Save the workbook, close it and reopen the workbook, now in the menu ribbon the ADD-INS tab is available with the VbaDeveloper menu
2334
'''
2435

2536
Option Explicit

0 commit comments

Comments
 (0)