@@ -10,11 +10,13 @@ Attribute VB_Name = "Build"
10
10
' 5. Enable programatic access to VBA:
11
11
' File -> Options -> Trust Center, Trust Center Settings, -> Macros,
12
12
' tick the box: 'Enable programatic access to VBA' (In excel 2010: 'Trust access to the vba project object model')
13
- ' 6. In VB Editor, press F4, then under Microsoft Excel Objects, select ThisWorkbook.Set the property 'IsAddin' to TRUE
14
- ' 7. In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'
15
- ' 8. Close excel. Open excel with a new workbook, then open the just saved vbaDeveloper.xlam
16
- ' 9. Let vbaDeveloper import its own code. Put the cursor in the function 'testImport' and press F5
17
- ' 10.If necessary rename module 'Build1' to Build. Menu File-->Save vbaDeveloper.xlam
13
+ ' 6. If using a non-English version of Excel, rename your current workbook into ThisWorkbook (in VB Editor, press F4,
14
+ ' then under the local name for Microsoft Excel Objects, select the workbook. Set the property '(Name)' to ThisWorkbook)
15
+ ' 7. In VB Editor, press F4, then under Microsoft Excel Objects, select ThisWorkbook.Set the property 'IsAddin' to TRUE
16
+ ' 8. In VB Editor, menu File-->Save Book1; Save as vbaDeveloper.xlam in the same directory as 'src'
17
+ ' 9. Close excel. Open excel with a new workbook, then open the just saved vbaDeveloper.xlam
18
+ ' 10.Let vbaDeveloper import its own code. Put the cursor in the function 'testImport' and press F5
19
+ ' 11.If necessary rename module 'Build1' to Build. Menu File-->Save vbaDeveloper.xlam
18
20
'''
19
21
20
22
Option Explicit
0 commit comments