One of the big complaints I get from clients regarding the vault is file
associations going awry after rename or move operations within vault by
other users who are opening up the old assemblies from their local
workspace. I know it has been talked about in the past but I thought I
would point out these common errors so others can avoid them. Depending on
how many users are working with Inventor, you may be able to "tell"
everybody to perform a Get Entire Folder on all the affected folders but
this is prone to human error as not everybody will do it immediately and
there may be additional logistics in getting a hold of everybody.
If you plan on doing any renaming or moving within vault you better be sure
of what files you are moving or renaming AND what the parent files are and
where they exist.
A common error: User A moves some files around in vault and User B then
opens up one of these files or a parent file from his local workspace.
Things seem to work fine, a red dot may appear whereby User B will perform a
get latest from Inventor. Even after a get latest, file associations will
not be correct as the parent assembly will still point to the old filenames.
It is imperative that if you work like this, then you never open up from
your local workspace and only open up from the vault.
I would go a step further and recommend that all the files that are being
affected by the vault operations not only be checked in to the vault (this
is a must) but also be deleted from ALL users local workspaces. That way
the users have no choice but to open up from the vault after these vault
operations have taken place.
I think it would be nice to have a better preventative measure for this and
was wondering how others handle these issues.
--
Rob
Inventor 2008 SP2
Vault 2008 SP1
ATI FireGL X2 AGP Pro
Graphics Driver: 8.223.0.0
(2 Monitors at 1280x1024)
Using Direct 3D
Intel Pentium 4 CPU 2.40 GHz
2.00GB of RAM