Vault Library Path

[Winks87]

Ok, I know this is a common thread but I still dont know why this is happening:

I have library folders in Vault mapped to a network drive (G:)

My Project clearly shows the Library paths pointing to network drive G:

(see attached images)

So, if I select a library part from the Vault and pick "get" it downloads to the C: drive.  Why?

I know we should open parts thru Inventor, but this is a method to edit library files if needed - I have a Library.ipj (non-vaulted) project for library part editing.  Since it is not a Vault project, I have to use "Get/Checkout" in Vault to bring parts over to edit.  Problem is they go to the C: drive, not the network G: drive.

Am I doing something wrong?

[ryan · Accepted solution]

In Vault Explorer, right-click on the Libraries folder and under properties, apply a working folder override so that it isn't picking up the C: mapping from above ($).

As an aside, unless you are in the process of transitioning into vault, there really isn't a good reason to have your libraries coming off of a network drive while everything else is from C:

Whenever I setup customer vaults in this scenario its always temporary, eventually this gets unplugged and libraries like everything else pull from C:

EDIT: In your screenshot, click the Change button under the working folder, that's where you need to set the path.

[Winks87]

In Vault Explorer, right-click on the Libraries folder and under properties, apply a working folder override so that it isn't picking up the C: mapping from above ($).

Our working folder was set to the C: by admin upon installation, cannot change this.  I can however "Map to Shared Server" in the space provided, but this does not change the download location. (see Vault Library 3 jpg)

As an aside, unless you are in the process of transitioning into vault, there really isn't a good reason to have your libraries coming off of a network drive while everything else is from C:

Wow.  Everything (and I mean EVERYTHING) that I read about using Library parts in a group environment states that these parts should be on a Network drive.  Maybe I left out the part about working with several other users...sorry about that if I confused you.

[ryan]

Map to Shared Server is not what you need.

You need to do either one of two things;


1) Abandon using Network-based libraries and instead, modify your IPJ file so that they are coming locally with everything else. This is by far the preferred option. This also enables the admin to keep the setting that the working folder is locked down. Again, best practice is to have your working folder location enforced administratively (e.g. C:\Vault Workspace or whatever) which in turn means that all of your vault data, including libraries, comes from this location.

2) Have your admin disable the setting with regards to enforced working folder which will then allow you to set the working folder override on your libraries as necessary. This is not the recommended route unless you are transitioning into vault. Remember that working folders are set on user by user basis so for consistency, after turning off this setting you then have to go to all workstations and make sure their working folder is set correctly (or copy XML file from machine to machine).

Ryan Small, Technical Specialist
1.877.438.2231 x110
2300 Steeles Ave West, Suite 240, Vaughan, ON L4K 5X6
[[image]]

[Winks87]

I think I am beginning to see the light.... as long as you have your ipj file set correctly, library can be on local C: drive, but still read only in Inventor.  I can set up a second project file where the C:library location is a workspace (if I have to modify files).