If I have a directory with 100s of files (parts, drawings, assemblies, etc.), I'll eventually get to a point where I want to have sub-directories with grouped items, like "Tooling", "Purchased Parts", "Drive Components", etc. After doing all this tidying up, I then will create a local search path file, "locsearch.pro". When I need to work on the assembly I load that search path file (its entries get appended to my current search paths), and then everything gets found when I load in the assembly.
This has worked for many projects, I even have a batch file I run that automatically creates the file so if I change the structure, adding or deleting directories, I can build a new "locsearch.pro" with a click. But, here's the problem: Apparently if a directory contains certain characters, the search path is not defined correctly. For example, the following line, even though it is enclosed in double quotes, does not work.
"\\network_location\Creo Files\Cheese & Stuff\Tooling"
It seems that the "&" character is "special" and prevents the path line from being properly interpreted, resulting in the dreaded "part not found" messages when an assembly is loaded. I can still traverse the directory structure to find the missing files manually, but that's what I am trying to avoid with the search path settings in the first place.
So, is there a list somewhere of characters that cannot be interpreted in search path designations?
