Skip to main content
1-Visitor
July 5, 2016
Solved

Search path config issue

  • July 5, 2016
  • 2 replies
  • 8961 views

Hello all, anyone have any idea why a search path config option keeps defaulting back to (null). This option worked fine, finding the directory it pointed to, in older versions of Creo, but in Creo 3 it keeps defaulting to (null). I keep opening my config file, i locate the search path option, i browse to the specific directory, i save the config file. All seems ok until i close out the session. When i fire up Creo 3 again, the option displays (null). Very weird. Any ideas?

Regards

John


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.
Best answer by BenLoosli

Try creating a search.pro file with your folder locations in it. Then replace Search_Path with Search_Path_File and point to the location of the search.pro. Use the full path name to the file!

SEARCH_PATH_FILE c:\creo_configs\search.pro

See if this helps.

2 replies

BenLoosli23-Emerald IIIAnswer
23-Emerald III
July 5, 2016

Try creating a search.pro file with your folder locations in it. Then replace Search_Path with Search_Path_File and point to the location of the search.pro. Use the full path name to the file!

SEARCH_PATH_FILE c:\creo_configs\search.pro

See if this helps.

1-Visitor
July 6, 2016

Thanks for your reply. I am experiencing some very weird behaviour here. I come into work today, & suddenly my search_path option appears to work fine, like it has done for years. Its worth mentioning, that I only started seeing this since installing M70 date code recently. I am having issues printing my drawings since updating too. If this falls down again, I will try your suggestion, but for now it appears to be ok.

Regards

John

23-Emerald III
July 8, 2016

A sample search.pro file would look like this.

p:\vendors\cummins\model

p:\vendors\detroit\model

p:\vendors\duetz\model

p:\vendors\kubota\model

p:\vendors\skf\model

plus whatever other directories you have parts located in.

In config.pro, you would have: search_path_file c:\ptc_user\search.pro

Since you have $CREO_COMMON_FILES\afx\parts\prolibrary\search.pro, try to open a command window and then CD $CREO_COMMON_FILES to see if it can find the folder structure. You may be better off hardcoding the $CREO_COMMON_FILES location as h:\engineering or whatever it actually is instead of using the variable.

I have found that PTC coders do not always use variable translation code when do OS functions.