I found an old internal PTC document about the change, which named the option Doug remembered. Ganesh, you may want to test with the hidden config.pro option "use_2001_search_order yes" (it still exists in Creo 2.0). But keep in mind that you have changed the default order, in case you get unexpected retrieval results at some point. After all the change to the order had been done intentionally, to avoid situations where you retrieve an assembly that has all components stored and end up with some components being loaded from the current directory instead. With this in place, when modifying and saving the assembly, some changes may be saved to a different directory than expected (the one that was current when retrieving). With the new method you can still replace components with those from current directory by opening them into session first, but it cannot happen unknowingly anymore. Gunter
"use_2001_search_order" has worked. With this option, Creo takes sublevel parts from my current working directory when I open assembly from other location which I wanted. Thanks Gunter, Doug and Antonius for your help.
This was a very enlightening discussion. Thank you for bringing it up, Ganesh.
Now I know I wasn't just paranoid... they really were out to get me
There is another wrinkle that caused us some confusion a while back. If you use the new failure resolve mode and use the "retrieve missing component" command, then Creo will remember the missing component's folder and add it to the search path - for the current session only.