Community
Firstly, you should not modify the acad20##.lsp or acad20##doc.lsp files in any way - as stated in the documentation, these files are reserved for use by AutoCAD and contain AutoLISP functions required by the AutoCAD application. Furthermore, any modifications can be overwritten following an update of the application.
All customisations to be loaded on drawing startup should be placed in the acaddoc.lsp file - and this file should be created if not already present on the user's system.
To determine whether an acaddoc.lsp file already exists, open a blank new drawing in AutoCAD and type at the command-line:
(findfile "acaddoc.lsp")
If the above returns a valid filepath, navigate to the file in Windows Explorer and modify the contents of the existing file as required.
If the above returns nil, open Notepad (or an alternative plain text editor) to a new file and populate the file with your customisations. When finished, save the file as acaddoc.lsp to an AutoCAD Support File Search Path (these paths are listed under the 'Files' tab of the 'Options' dialog), ensuring that the 'Save as Type' option is set to 'All Files'.
When a drawing is opened (new or existing), AutoCAD will automatically search the working directory & all support file search paths (in the order listed in the 'Files' tab) for a file called 'acaddoc.lsp'; AutoCAD will then automatically load the first such file found into the current drawing session, hence evaluating all AutoLISP expressions contained in the file. More information about the potential dangers of such behaviour can be found in my post entitled: 'Dangers of the acaddoc.lsp'.
Now, regarding your code: as Matt has correctly indicated, the error you are receiving arises because the ActiveX component of Visual LISP has not been loaded using (vl-load-com) prior to invoking an ActiveX function - in this case (vlax-get-acad-object). Hence, you will need to ensure that (vl-load-com) appears in the file (and is evaluated) before calling an ActiveX function.
Looking at your expressions to add new Support File Search Paths (SFSP), I note that there is no check to test whether the added support path already exists in the list of SFSP and so, when the code is evaluated again (i.e. when the AutoCAD application is restarted since your code currently resides in the acad2013.lsp file), these support paths will again be appended to the list of SFSP.
To offer an alternative, consider my set of Support File Search Path functions; using my LM:sfsp+ function you can add a list of support paths in one expression, with the guarantee that if a path already exists in the list of SFSP, it will not be added twice, and paths which do not exist will also not be added.
Furthermore, the use of my function will be far more efficient in its operation, since it does not repeatedly call vlax-get-acad-object (which is a slow function to evaluate and repeated evaluation of this function should be avoided where possible) and then trudge through the Object Model hierarchy (application > preferences > files) for every support path.
To demonstrate the use of my function using your support paths:
(LM:sfsp+
'(
"S:\\Acad2007\\Lisp"
"S:\\Acad2007\\Simpson\\Menu"
"S:\\Acad2007\\Hatch_Patterns"
"S:\\Fonts"
)
)
I hope this helps.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
