COMPANY PROFILE SYSTEM VARIABLE OVERRIDE

[neabailey]

Good morning all, My company Profile has set the SSMsheetsetstatus system variable to 0. I want it to be 2. Below is what it does. 

Value Description
0 Do not automatically refresh the status data in a sheet set
1 Refresh the status data when the sheet set is loaded or updated
2 Refresh the status data when the sheet set is loaded or updated, or at a time interval set by SSMPOLLTIME

Is there a way to add a lisp that loads with each drawing to change it back to 2? I want to basically "override" the profiles setting.

~nic

[Kent1Cooper]

---

@neabailey wrote:

....Is there a way to add a lisp that loads with each drawing to change it back to 2?

---

That is what an acaddoc.lsp file is for [to load things in every drawing that is created or opened].  If you don't have one already, and if it's allowable to violate company standards that way, make acaddoc.lsp with a plain-text editor such as Notepad, in a support folder location that AutoCAD knows to look in.  Put this in it [including the correct spelling of the System Variable name!]:
(setvar 'SSMsheetstatus 2)

[neabailey]

@Kent1Cooper  Good catch on the spelling, whoops. So our profile auto loads a bunch of or standard lisps from the standards directory, and one of them is the acaddoc.lsp file. So can I create one with the same name and load it on from my Personal lisps folder?

[Kent1Cooper]

I think it will do what's in the first acaddoc.lsp file it finds, so if it sees "yours" first, the other settings/loadings would not happen.  I guess you can't put that one setting into the shared file if not everyone else agrees about it.  But can you sneak in a line that checks for the User name, and only if it's you, changes that setting?  Or can you make a copy of the shared file with that added, and put it higher in the support file search path so it gets seen first?  The latter would mean you need to keep up on any changes to that shared file.

[john.uhden]

@Kent1Cooper 

Been there; done that.

The problem is that every computer that needs this fix has to have the code in each of their acaddoc.lsp files if they are local.

What I did for one company was to change each of their acaddoc.lsp files to include one line...

(load "<network path>\\<your file name>")

where that file contains all the custom operations and/or functions you want to have performed/defined.

BTW, did you know that an AutoLisp file does not have to have an extension of ".lsp?"  But you have to include the extension in your file name if it isn't ".lsp."

I haven't tested to see if that is true for .fas and .vlx and .dcl files.

[Sea-Haven · Accepted solution]

Skip acaddoc and do appload "Strartup suite " add the lisp there to load on each startup I have been using this for years I do not know why people are obsessed with acaddoc.lsp do an upgrade and you acaddoc is not relevant any more. Make one loadonstartup.lsp Ok it may take a couple of minutes but my Start up suite has one lisp, inside this lisps are multiple (load "my lisp") so more than 1 lisp file is loaded, providing they are not ran at time of start up you have no problems.

Just checked my lisp file 

38 defuns

14 load lisps

You know where file is you know what is in in it. is it really that hard !

Oh wow watch the criticism !! works for me 40+ years with Autocad.  

[neabailey]

@Sea-Haven this is exactly what I ended up doing. Works perfectly, I have around a dozen separate lisps in the appload start up. I can't see a down side.

[Kent1Cooper]

---

@Sea-Haven wrote:

Skip acaddoc and do appload "Strartup suite " add the lisp there to load on each startup I have been using this for years I do not know why people are obsessed with acaddoc.lsp ....  

---

Here's why I use acaddoc.lsp instead.  From Help:

And similarly elsewhere:

The same kind of wording is used in description of the optional acad.lsp file:

I haven't found similar wording to the following specifically in relation to what's in the Startup Suite, but since that is described above in the same terms as acad.lsp, I assume this would apply to it as well as to acad.lsp:

There may be some kinds of things loaded only when the product starts that "stick around" to be available in drawings other than the first one opened, but for AutoLisp routines I don't count on it, so I go with the green.