load options question

[loworange88]

Hey everyone,

I have set up a load options file for NX6 to search through a few different areas, which is great for our reuse library. The problem I am facing, is that for so long and before my time, all the options were always set up with just "from folder" So over the years, there is multiple copies of the same thing all over the place. I have cleaned up alot of that stuff, and I have what I think is a good procedure in place to help prevent this. I was wondering if there is a command for the load options that will search the current directory that I am opening an assembly from. such as a .\... ? Then have it look at the other locations I have specified.

Where I work we have everything broken down into smaller assemblies, in "work folders", so I would love the search options to first and foremost look at the directory I am opening from, then search through the library and archive folders.



Thanks, Mat

 

[looslib]

I see a problem in using ./... in search paths and that is where NX picks up for the top directory in your search. It will be different depending on certain conditions.
The top level will be where NX starts from/loads a file, if you double click on the part file icon.
The top level will be the Starts In directory of the NX icon on our desktop.

I do a double load in these cases. First is to use From Diectory to get those files. Second use Search Paths to get the files that reside in the library and archives.

Use the Assembly-> Reports-> List Components to check the location where NX opened the file from.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[JohnRBaker]

Without creating some customized code which would be used to open you assemblies, I can't think of way to accomplish what you wish in a single operation, although we can see the value in it, just that we have never provided a 'token' which would represent the 'folder from which I just opened the assembly from', unlike '.\' which will give you 'folder from which NX was launched' or '\...' which give you 'all the sub-folders'. Sorry.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[hudson888]

Basically from long experience we have found that within reason the fewer folders that you have to search the better. I think you may do better to rationalise your file storage strategy in ways that reflect your workflow and processes.

There are also implications of structured directories that would be particularly important for anybody using file name versions in NX. The system interrogates the directories from the top down finding the first core file name match and comparing it with other versions in the same directory before making a choice of which one to load. If there is a later version in any sub folders it will NOT be loaded.

Some food for thought. By all means contact us if you need further assistance.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[loworange88]

Thanks for the input everyone. I think we are going to look at the double load options, or even the "as saved" option, I've tested a few things, and so far the "as saved" method seems like it is doing what I want. I will test it more and more, and check my reports for load locations.

Thanks again.

 

[looslib]

One note on the search path order. Any sub-folders when using /... will be searched in CREATION order, not alphabetic named order.
So be aware if you use this method and happen to have multiple files of the same base name in the folder structure.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli