PROJECTNAME Variable dilemma

[stusic]

We use the PROJECTNAME variable in our menus here at work and generally it works well for loading the appropriate references, LISP routines and menus. The problem is since this is a shared menu (so it can easily be updated), the end-operators have absolutely no control in customizing their environment (toolbars, command aliases, crosshair size, etc.) without changing verybody else's environment. As it stands now, we have to all agree on changes in toolbar layout, command aliases and any other options before it is implemented. This seems like a big waste of features that many operators rely on. I am a screenhog (probably stemming from my days of AutoCAD without toolbars) and would like to load the projects like we do now, but also be able to get rid of the vast majority my toolbars.

My question is this: Is there a way that we can do something similar to setting up projects the way we are- keeping project paths intact- but leaving individual customization available to the operators?

Any help would be greatly appreciated!

Thanks,
Phillip

[Mike.Perry]

Hi

Am not sure how system variable PROJECTNAME fits into this, as far as I'm aware PROJECTNAME only aids in the loading of Xref's & Images -

ID: TS69565 - Set up PROJECT feature

******

If you're on a Network I would recommend that you look at centralizing all Standard AutoCAD files there, then point all User's to the Network locations (makes for far easier management in my humble opinion). Things like -

Acad.mnu (Base menu)
Native AutoCAD Font Files (SHX)
Hatch Patterns (PAT)
Linetypes (LIN)
Plotter Configurations (PC3)
etc

Have a browse of the following threads, should offer one or two more ideas -

Transfering Toolbars

Centralizing & No More Time Wasted on Support

Multiple printer configuration file search paths

Location for fonts

when is it enough?

standardize office

Exporting & Importing Plotter Settings

page setup

LOST ACADISO.PAT LINK

+

Further searching within the Forums will turn-up a lot more information -

Search Forums

+

To give User's flexibility look at things like -

Custom.mnu & Custom.mnl (Partial Menu)
Own individual location for Plot Style Tables (CTB or STB)
Acad.pgp
etc

Have a good one, Mike

[stusic]

I'm sorry, after reading my own post a couple of times and looking at the response, I realized I made a critical error: The PROJECTNAME variable is NOT located in our menu, it is a set variable saved in a shared profile. It's this profile that keeps us from doing any sort of customization. The only reason we have the PROJECTNAME variable enabled is to maintain file locations and their hierarchies. My question should have been "Can we maintain the things the PROJECTNAME variable does and load it with all users without keeping it in a profile? Having to load this profile severely limits anything a user would like to do to their drawing environment.

Thanks a Bunch!

Phillip

[Mike.Perry]

Hi

First thing - There really is no need for the "sorry".

Have a browse of the following thread, hopefully will give you some ideas -

Project Support Search Path

Have a good one, Mike