Hi
I have an answer to this question, plus another related question:
In my experience with Wildfire 2,3 and4+ Intralink 3.4, breaking up family tabled parts has no ill effects in higher-level assemblies: I've seen them all open OK and find the parts as required...
At our place, I'm breaking up many library part tables that have grown over the years and caused many issues with Intralink. My question is: as we look at migrating to PDMLink 9.1, is there anything to watch out for??!
Regards
Edwin Muirhead
CAD Manager, Weatherford
In Reply to Vaughn McDaniel:
WF3, Ilink 3.4 m030
I was rather sure that breaking up a family table had no ill effects on
assemblies that are using the instances.
However, i have some assemblies that do not find the stand-alone parts, it
still looks for the instance with that name in the generic.
This is resolved by manually opening the missing model in failure mode.
Strange though is that I have to do it for every occurrence of that part,
lame.
Anyway, to the question.
If you break up a family table, the assemblies using those components
should open and find all the models, right?
Some of these assemblies are rather old, my only experience has been with
WF3, Ilink 3.4, is it possible 2000i had an issue with this?
Vaughn McDaniel III | CAD/PDM Administrator | Kärcher | Englewood, CO |
303.762.1800 x187
