@GISDUDE: Did these explanations give you insight as to you question?
I'm guessing your ondocload.lsp is very close to Stefan's code in the 3rd post (perhaps using load instead of autoload). But your question was how to get your ondocload.lsp loading ... right?
Anyhoo, there's quite a few methods, but the most robust & portable one is to include a statement in the acaddoc.lsp file (this might be a file you have to create as it doesn't exist by default). Please never alter the existing acaddoc20##.LSP file. That one's ADesk's file and could change at any time due to updates / upgrades - effectively erasing your edits. The acaddoc.lsp and acad.lsp files are deemed to be your own and adesk will never touch them.
Assuming your ondocload.lsp is in a support folder, the following code in the acaddoc.lsp should be sufficient:
If the file isn't in the support folders, and for some reason you don't want to include it's folder in the support path, then you'll need to add it's path in that load statement.
Another point is if your load statement has no 2nd argument (as the sample above does), then loading a LSP file with an error in it will propagate the error into the file loading it. So if there's an error in the ondocload.lsp file, then the above will cause acaddoc.lsp to stop at the load statement. A way of getting around this is to include a 2nd argument:
This way if there's an error, the load function simply returns the 2nd argument (in this case nil) and lisp continues to the next statement without erroring the whole acaddoc.lsp file. This might be why your ondocload.lsp is a separate file - to avoid other customizations failing to initialize if something else fails.
Other ways of including your file might be to add it to the StartUp suite (AppLoad command), though I'd not advise this as it tends to give strange results especially on shared folders. Or you could add the file as a lisp to be loaded in your CUI. Or add the load statement into a MNL file named the same (and in the same folder) as your CUI(x)/MNU file. My personal favourite is the MNL idea, since it ties nicely with my custom toolbars/menus/ribbon panels - i.e. all I need to do to "install" my LSPs is to load my CUI (which I'd have done anyway to add the toolbars/etc. through the CUI command or MenuLoad command). The MNL file works much the same as the acaddoc.lsp, though it need not be in a support folder - only in the same folder as its CUI.
As for using load / autoload - it depends on your preference / scenario. Load immediately loads the LSP/FAS/VLX file, while autoload creates a temporary defun which calls the load only when the command is executed. Note though that the built-in autoload has some issues with paths, I'd recommend that if you use it all your LSP files need to be in a folder under your support paths.
