Search Path Ordered List 1

[markborges]

Hi all,

I am about to test an ordered list of search paths on Wildfire 2.0. Has anyone had any experiences with an ordered search path working or not working. In other words I have a large assembly in which we are starting rev 3; ie., rev 3 of the truck is to redesign an assembly behind the cab. I want the top level assembly to pull in my new "behind the cab" assembly and then pull in all the assemblies/parts from rev 2; which constitutes, drive line changes, and then pull in the rest of the truck.

I plan to do this with ordered search paths; ie., my working directory will be set to rev_3 files which has the top level assembly file and any random files that were changed and designated as rev_3 changes. My config file will have ...\rev_2 and right below will be ...\rev_1. I expect a complete truck to pull up, with my "behind the cab" assembly, the rev 2 driveline and all the unchanged parts/assemblies that were left in the rev_1 directory.

Has anyone had any experience with this? Is there a better way to do it. I ask because our file structure is really more complicated then this and I hate to do alot of directory restructuring only to find it won't work.

Thanks as allways to the ProE gurus.

Mark

 

[dschaefer]

There's a default search order that Pro|E uses that will liekly help you out. It changed with WF and there's a hidden config option to switch it back.

When opening an assembly in WF the order that Pro|E looks for the parts and subassy's is:

1. In session (in memory)
2. Directory containing the assembly or drawing file
3. Active Windchill or Pro/INTRALINK Workspace and Commonspace
4. Current working directory
5. Directories in the search path

Prior to WF #2 & #4 were swapped & #3 isn't listed at all. Set 'use_2001_search_order' to yes to restore that behavior. There's a KB article on it here.


Doug Schaefer
Design Central
Columbus, OH