Search paths 1

[aafuni]

I know this has been discussed here before, but throughout the years I have never had any luck with search paths.

So, I have an assembly at "D:\Pro E\...\deflector" and a bunch of bolts in that assembly are at "D:\Pro E\Common". I have a search.pro file with a single line:

search_path D:\Pro E\Common

I then have a config.pro entry "search_path_file D:\Pro E\search.pro"

Every time I open the assembly the bolts are never found and I have to manually point it to the common folder. For good measure I even added the "search_path D:\Pro E\Common" directly to my config.pro, with no luck.

I am pretty sure the issue is coming from the space in my Pro E folder name. If I move the common folder to the drive's root and adjust my search path accordingly, it works no problem. Is there some way I can notate this folder in a way that it will work?

I am currently running WF5, but never had luck with WF4 either. I am running WIN XP 64bit.

 

[robertib]

All you need in you search path file is

"D:\Pro E\Common"

 

[aafuni]

robertib,
That doesn't work. I think it can't have spaces, but I don't want to rename it and have to redirect everything in that folder.

 

[looslib]

1) Search_path_file only points to the folder that contains the search.pro file.
2) Spaces in names are a know issue with PTC products. Rename your folders and files to eliminate spaces in the names.

If it works, renaming the folders won't hurt, becasue WF will now pick up the components automatically and you will save yourself the frustration of manually locating your common parts.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[aafuni]

I know both of those things and as I described I have a search.pro file at the location I stated in the search_path_file location. I guess I was wondering if there was a way to make Pro/E accept the path with spaces, through a space character or relative paths or something. In my Pro E folder I have several Pro/E files that are called from Excel Vba scripts that have paths written into them. For that reason I can't just rename the folder.

If there isn't a way around this I will just have to put my common parts folders on the drives root. For what ever reason I can put the search.pro file in a folder with spaces and it finds that no problem. It is only a problem finding the common folder with spaces.

 

[dgallup]

I know I have seen this work. If the double quotes doesn't work try single quotes. It can be done.

 

[robertib]

I forgot to mention yesterday to enter the entire line, including quotes. We regularly use spaces in directory names, and using double quotes works (at least on Windows XP, presumably all version of Windows as well).

 

[RBobroski]

This may sound simple but could be overlooked: are you sure you are starting pro/e in the same directory as your config.pro file? Select Help - > System Information to make sure the correct config.pro file is loaded.

 

[dgallup]

You can go to tool/options and see all the loaded config.pro options, which file loaded them & if they are valid (Green status indicator).

 

[aafuni]

Single ' did the trick. Thanks guys.

Rbobroski, I'm not that bad, I have been using Pro/E for years now.

I have been pretty diligent about not using spaces in my folder names since back in the WF3 days it seemed to really goof things up. I somehow missed the fact that my root working directory had spaces when I moved everything over to the new computer.

 

[RBobroski]

Hey, you never know. I wasn't calling you inexperienced. When I first started at my new company the IT head mapped by I and T drives backwards from the way the old design engineer had them mapped and it was driving me crazy until I caught this little glitch. I still had the I and T drives, they were just backwards and none of us caught it. Simple mistakes always seem to hamper even the most technical individuals sometimes.