Ah...Old School ways of doing business!
Basic points:
Folder hierarchy will be important.
Keep standard parts in a separate folder with search paths pointing to it in a "corporate" config file that load when your users start up.
Make standard parts "read only".
For individual users on an individual database, no real issues. Create a folder for the project that is the vault. Have the individual "pull" in a copy and work locally. Save at the end of the day back to the "vault".
For multiple users on the same project is where strategic "saves" get interesting. Same setup. Use the "vault" method. Users can pull the assembly into their respective sessions and work on their parts as they wish. You may need to set the save criteria for parts. I think this is now called set_model_types_to_save in the config file. This used to be "Save Objects" and we could set different save criteria. However, you may not need to do this. Essentially when one person needs to save their modified parts they need to communicate that to the team. Team member "A" saves their changes and then erases everything from session. Team member "B" saves their modified parts locally. Then "B" "pulls" the updated assembly BUT makes sure they have their modified parts "in session" first before the "pull". Open the latest assembly, save it to the "vault". This way both "A" and "B" have saved their work without messing up one another's work.
Hope it makes sense.
