I couldn't stand the pancakes, as I had literally hundreds of different palettes.
So I have been using this way to create an enterprise solution for the last 8 years:
First, I created a custom toolbar (I know, old school)
Then I created an empty directory that I wanted a palette in: In the example below, that directory was S:/ACADBLKS/TOOL PALETTES/Civil/Bus
Then I set a number of buttons up to handle each palette that would coincide with what I needed to work on: Each of those could have tabs in them, but I wasn't willing to fight a very large stack. I just add more buttons...
the code attached to each icon on the toolbar looks like this:
^C^CToolPalettesClose;*_TOOLPALETTEPATH "S:/ACADBLKS/TOOL PALETTES/Civil/Bus";ToolPalettes
What I am doing is changing the current path of the palette on the fly, depending on which button on the toolbar is selected.
Also, I wanted the users to be able to manage their own palette, which would affect no other users on the network.
For this, I created a button which sent the current user to their own palette/directory, by using this sytax:
^C^CToolPalettesClose;*_TOOLPALETTEPATH (strcat "S:/ACADBLKS/TOOL PALETTES/User/" (getvar "loginname"));ToolPalettes
I plaeced this one out on the network as well, as I wanted all customizations to be backed up regularly and that doesn't happen on our local machines.
This may be more that the original poster wanted, but it does give the best of both worlds.
If all you want is one palette, set the environment variable TOOLPALETTEPATH in the options dialogue box to an empty directory and create from scratch.
Thoughts?
d.