Assembly won’t find the parts

[MB2011SD]

I have updated the search_path_file so it will go to the directory that has all the parts for my assembly, but even after I did that, when I go to open my assembly, there are still a few items in "red" which I have to go retreive manually. All the parts are located under one directory, so I don't understand why I keep having this problem.

If anyone has any advice I would appreciate it.

Note: The .prt drawings that I need for my assembly, are located in "subdirectories" of one "main directory", but to me, even if it's in a sub-directory, it should still find the parts. In other words, I have one directory called "parts" (And I am telling CREO to look for what i need in "parts", but below that parts directory are sub-directories called "bearings, cylinders, etc".

Shouldn't it work with no issues? even if the parts are located in sub-directories below the directory I am telling CREO to go and look?


Edited by: MB2011SD

 

[D. Urban]

Sorry, you will need to add the complete subdirectories paths to the config.pro file "search_path"
<?:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" />
Although I think that is a good thing, quite often I

 

[MB2011SD]

Okay but I did add the subdirectories as well, and it still didn't work. I actually tried having 3 or 4 search paths where my parts were located, and it still didn't work...but thanks.

i can even set my working directory to be the exact directory that has certain parts, and when I open the model it STILL won't just find the parts. They are right there in the working directory, but in my model, it acts like it can't find them.

I noticed if I manually go retreive the parts, my computer will remember this. But if I close CREO, and then open it again, the assembly starts over like it has no clue where the red (missing parts) are.
Edited by: MB2011SD

 

[D. Urban]

I hate to mention this because it sounds so dumb and unbelievable, but years back I would periodically have problems with search paths when I typed the path manually. (Yes it was correct) however I found that copying the path from explorer and pasting it in would make it work.<?:namespace prefix = o ns = "urn:schemas-microsoft-comfficeffice" />
Now it

 

[MB2011SD]

thanks i might try that. It does allow you to "browse" for a directory. Perhaps that would help.
I thought about trying that.

 

[D3syn3rMike]

Silly question,but are you updating the config.pro file or the search.pro file? You ought to be able to leave the config.pro file alone and add paths to your search.pro file as needed. This depends on whether you're using the "search_path_file" option or the "search_path" option. You can use both, but they work differently. "search_path_file" directs Pro/e to a specific search.pro file listing specific directories, this file is separate from the config.pro file. I think "search_path" lists directories directly in the config.pro file. In both cases it is wise to include full path names in quotes, and I agree wtih D Urban on the copy-paste method. Also,I think I read somewhere that Pro/E won't recognize paths over 260 characters.


Changing the working directory will tell Pro/e to look in the new working directory (no subdirectories) and any directories identified from the last loaded config.pro file, it does not automatically change config.pro settings.If you started Pro/e in one directory and then switch working directories, Pro/e still operates using thelast loaded config.pro and search.profile(s).And ifthe config.pro/search.pro file(s) do not identify the directories needed for your assembly, then Pro/e won't load the parts from those "missing" directories automatically, you'll have to load them manually.


I suggest creating a config.pro file specifically for this assembly in the folder where the top level assembly file is. In that config.pro file, list the directories using the search_path option and/or create a separate search.pro file, list the directories in it using full paths and quotes, and then set the search_path_file option to that file using the full directory path and file name (C:\Mydocs...\search.pro). Then, when you start Pro/e and set the working directory to that assembly's folder, load your new config.pro file through tools >> options before opening the assembly.


Sorry, that's a lot to read, andsorry if thatadded to the confusion.

 

[dr_gallup]

I always create a config.pro in each project directory with any project related settings including search paths. The first thing after Pro/E starts we change the working directory to the project directory then we load the config.pro file. Works every time.

Do you have any spaces in your path names? If so you have to quote them so Pro/E can read them properly. Don't ask me how to do it, I never allow spaces in path or file names. Saves so much trouble.

 

[dr_gallup]

There's your problem.

Pro/E (Creo) will not automatically search sub-directories.