We had this exact same issue.
In our case, we created the vault view in the users MY DOCUMENTS folder, While this is convenient, TOOLBOX did not work correctly for copied parts.
I think the only solution is to create the vault view in exactly the same location on each person's machine.
In our case we relocated the vault view to C:\VAULT on everyones machine.
Brian is correct. All of your client machines should have the same location for the vault. That keeps the file structure the same for our CAM software as well so kits with referenced parts can be located automatically without browsing. Think of SW in windows explorer if you move an assembly....
Ours is C:\Vault Views\<vault name>
That way you can have multiple vaults. We have our company vault and a "sandbox" vault that I can mess around with workflows before implementing.
Thanks you getting back to me Gents, It seems you're both right - Solidworks doesn't accept Conisio:\\ links for folder locations.
I'm going to make sure that all our Vault lcoations are in exactly the same place. Though it would of been nice to have a solution.capable of handling any errors.
Do you have any further hints and tips for network installation of SolidWorks? Specifically folder and template loactions and the Vault?
Thanks for your help,
Templates - Have one folder in the vault for your part, assembly, and drawing templates that everyone's SW points to for default template. Ours is C:\Vault Views\<vault name>\Templates That should have read only access for your users, more access for your CAD/ePDM admins, Also, under cache options for the engineering group I have it checked for "Refresh cache during log in" so they are always pulling from the most recent version.
As far as folder locations, I've found the easiest way for us is limit the number of top level folders. We have top levels for our company (with all the customers below in folders), DXFs, Library, CAM Files for programming, Templates, Tooling info, and a WIP folder which has folders for individual engineers to store things, work on parts/ideas before assigning a "real number" to. Then you limit permissions/visibility per top level folder based on needs.
You'll find that folder structure doesn't matter nearly as much as before ePDM. I rarely dig looking for files going through file structure, 95% is done through search cards. I'm still trying to teach old dogs new tricks about this fact.
Thank you for taking the time to offer me your advice Craig, it's more than appreciated.
I have located the Vault in a common location across all users - we still haven't upgraded from 2012 SP5 so I don't believe the 'refresh cache during login' option is available to us, but that's definitely something I'd like to introduce when we do make the switch.
Craig Schultz wrote:
... and a WIP folder which has folders for individual engineers to store things, work on parts/ideas before assigning a "real number" to.
I know this is an old post, but how is this handled at your company? I'm interested in implementing something like this in our vault to help stem the creation of "xxxx_test" files in our project folders, because it's starting to become extremely cluttered. Do your users create a part for initial design/testing then rename and move it to the correct project folder once it's complete? Or do they create an initial part, then once it's complete do a "save-as" to the correct project folder with the correct filename? Do any of the file references ever get messed up with your setup?
I've got some people creating test parts in the project's folder, then just changing the filename to "NOT USED" once they're done. Other people create parts on their desktop and try to save it in the vault when they're done, but then sometimes they forget or file references don't update, so it ends up looking for the part on their desktop still.