I've never experienced any problems with a search.pro file myself. Nor have any of my co-workers until just recently. One of our machine designers has a network drive mapped to be able to access another machine designer's files at a remote facility. The permissions to the files are wide open for the world--set by the creator of the Pro/E objects. The user that is experiencing failed assembly model retrievals has his config.pro file in his Pro/E startup drive/folder location. No problems there. And it has the 'search_path_file' option set to the same drive/folder--and points to the file named 'search.pro'. No problems there. With that said, could someone please provide me with some tips on what could possibly be causing the end user's assembly model retrievals to fail--due to certain assembly components not being found? Do the 'search.pro' file's entries have to be in alphabetical order? Any insight into why this guy is have this problem would be greatly appreciated. I'm going to try and help him out since he's a new user.
Thanks all!
J. Perry