Search Paths

[DL_allainmfg]

Hi,

I'm looking for a way to map search paths so that Pro does not only look in the folder I have mapped, but also in the sub folders within the mapped folder.

Is there some kind of a command that would allow me to do this ?

Thanks

 

[jnoval]

make at batch script:


dir /b /ad /s >search.pro

 

[DL_allainmfg]

I thought I had it but I didn't...should the command look like this inside of the search pro.

Y:\A_START_PARTS\Manufactured Parts /b /ad /s


Thanks

 

[looslib]

No. In serach.pro it should be Y:\a_start_parts\Manufactured Parts...


The '...' tells Pro/E to look in sub-folders.


Be careful of folders with spaces in the names. I don't trust CAd companies to be fully MS compliant in this aspect of file/folder naming.

 

[AHA-D]

Looslib,


ProE is not Windows based, only windows "channeled", so you're absolutely right not to trust anything.


Furthermore, search paths are IMHO one of the things that can cause a major slowdown on network drives. Any user will cause a major load on the server when opening an assembly that has lots of parts scattered along the different search paths. Remember that ProE has no clue where the part will be found and that directories "in motion" (changing content) need to be reloaded each time.


Alex

 

[dr_gallup]

No. In serach.pro it should be Y:\a_start_parts\Manufactured Parts...


The '...' tells Pro/E to look in sub-folders.


Be careful of folders with spaces in the names. I don't trust CAd companies to be fully MS compliant in this aspect of file/folder naming.

I can't get that to work, also tried Y:\a_start_parts\Manufactured Parts\...

That did not work either. Straight WF2, no PDM.

 

[jnoval]

My solution was to make a script that will make the search path file for you in a "automatic" way.


Try to emove the spaces in the folder naming.


I think Config.pro must tell ProE where the search path file is located

 

[looslib]

Yes, there is a config.pro setting to specify the search path file name. It is: search_path_file and points to the file that has your search paths in it.


I just checked the search.pro file that we used, and it just has the path: p:\vendor\company1, p:\vendor\company2.