@@ -9,17 +9,28 @@ Attribute VB_Name = "Build"
9
9
' 3. Rename the project to 'vbaDeveloper'
10
10
' 4. Enable programatic access to VBA:
11
11
' 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
13
16
' 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'
15
18
' for 'Excel 2007 and later Macro-Enabled Workbooks and Templates'.
16
19
' 5. If using a non-English version of Excel, rename your current workbook into ThisWorkbook (in VB Editor, press F4,
17
20
' 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
19
22
' 7. In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'
20
23
' 8. Close excel. Open excel with a new workbook, then open the just saved vbaDeveloper.xlam
21
24
' 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
23
34
'''
24
35
25
36
Option Explicit
0 commit comments