Relocating Files

[MichaelEwer]

I currently have a bunch of Solid Edge files in one giant folder. I am interested in relocating these into several different folders to make different parts easier to find. But when I move a part to a new folder, my assemblies don't know where the part went. Anyone know how to get around this problem?

 

[beachcomber]

I think this is a job for Revision Manager, but it's going to take a bit of work.
First question - is there a top-level assembly that links all these files, or are there several top-levels?
If there is only one, then you should be able move the files easily with Rev Manager, and maintain the links.
If there are several, could you create a single top level, or would that be too big?
What about drawings?
You shouldn't really just move files with Windows explorer.
You may need to use a Link Management file, but let us know how many files etc you have, and we can give you the best solution.

bc.
2.4GHz Core2 Quad, 4GB RAM,
Quadro FX4600.

 

[KENAT]

Revision Manager.

There have been several posts in the last few months about revision manager so look at those.

Think long and hard before sticking stuff in sub folders, Solid Edge is 'happier' with a big flat folder.

thread562-210643
thread562-215471
thread562-226494
thread562-212959

KENAT,

Have you reminded yourself of faq731-376 recently, or taken a look at posting policies:

http://eng-tips.com/market.cfm?

 

[MichaelEwer]

Thanks for the replies guys. I think there is one top level, which includes maybe 10 subassemblies. These subassemblies then include other subassemblies etc. Probably 100-200 unique parts with maybe 500 total parts (some are used multiple times). Currently all in one flat file, but we are starting to restructure how we save files, and one desired feature is to have each subassembly in its own file. So it would look like this

Top Assembly
Subassembly1
Moresubassemblies1
Subassembly2
Moresubassemblies2
Subassembly3
Moresubassemblies3
...
etc
Located in each of these folders would be the parts for that individual subassembly. Do any of you follow this structure?
...

 

[KENAT]

We sometimes do similar during development.

(Note: before you do this play around with a set of dummy files etc. and read all the above links with information on revision manager and any other info you can find. Once you know how to use it rev mgr is a great tool for managin unmanaged files. Until you know how to use it, it's almost as dangerous as just using windows exporer.)

Are all parts unique or are some shared between completely separate sub-assemblies, such as hardware?

Simplistically if all parts & lower level sub-assys for each sub assy are unique...

Create your folders.

Open the first subassembly with rev mgr, expand all, select all, set path to new folder.

BEFORE you perform actions select all and do a where used search. (To speed up the where used be selective of where it looks and what file types, in your case probably only drafts and assemblies)

Set actions for all items found by where used. EG, for top level assy you might just want to update, for any drawings maybe you want to move them to the same folder so you'd do a 'set path'.

Perform Actions.



KENAT,

Have you reminded yourself of faq731-376 recently, or taken a look at posting policies:

http://eng-tips.com/market.cfm?

 

[beachcomber]

"one desired feature is to have each subassembly in its own file" - where do the parts go if they are used in more than one sub-assembly ?
I wouldn't seperate assemblies from parts, except in the case of hardware/standard parts.
It becomes a PITA changing folders when creating/saving new parts and you will always end up with them getting mixed.
However I would keep drawings seperate to models.
It doesn't matter where drawings are moved to as long as the models stay in the same place (an advantage of one-way associativity).
If there is one top level my procedure would be
1. Open top-level assy in Rv Manager
2. Expand all
3. Select all
4. Set action to Rename
5. Set the paths to the appropriate folders (use the 'Select Files' command - the one next to where-used - if necessary)
6. Select all and do where-used to find the drawings.
7. When it's done, click in one of the column headers in the bottom window (this will 'activate' that window)
8. Click the 'Select Files' button.
9. Change the *.* to *.dft* then OK
10. All the draft files should now be highlighted.
11. RMB on one of the highlighted files and set action to Rename.
12. RMB then Set Path for the selected draft files.

This SHOULD move everything and maintain the links.
BUT - as KENAT says, GET FAMILIAR WITH REV MANAGER BEFORE DOING LIVE DATA.

If you don't have a single top-level, it may be an idea to create a temporary one. Alternatively you could create a draft file and attach a single view of each top-level, then open this draft in rev manager.


bc.
2.4GHz Core2 Quad, 4GB RAM,
Quadro FX4600.

 

[MichaelEwer]

Okay I'm starting to look into revision manager, have never looked at it before. But I'm not using drafts really. Are you suggesting to keep all my parts where they are but put the drafts into the different subassembly folders? The sheet metal/plastic place we use for manufacturing doesn't require any parts to be drafted, so I don't really have drafts.

So when you guys are modeling parts for a project, every single solid edge file regarding the project (aside from standard parts) are located in one giant folder?

 

[beachcomber]

Generally that's the way its worked wherever I've been.
All 'standard parts' in one set of folders (with seperate sub-folders for bolt, screw, washer etc), then all the 'project' parts in another folder.
If the project is small (as yours are) you could keep the drafts with the models (as we did at my last contract).
If there are lots of drafts (we had ~1000 drawings per project on a previous contract) you could create a sub-folder for the drafts.
I don't know if anyone else has thoughts on this - it would be nice to get several opinions.
In the end, it's what your company wants and feels comfortable with that will determine the method.


bc.
2.4GHz Core2 Quad, 4GB RAM,
Quadro FX4600.

 

[PatCouture]

I prefer having only one folder for all solid edge files specific for the project, and of course as said seperate folders for standard parts.

I already tried to put parts in subfolders and didn't like it. I'll most likely open the top assembly and search for part numbers in there anyway.

As Kenat mentionned SE prefer one flat folder and the reason is, he will always check inside the current folder for parts, if they aren't there then he will check the fullpath.

Patrick

 

[KENAT]

Beach, the reason I suggested opening each toplevel sub-assy separately in rev mgr is so the select all functionality can be used rather than having to individually select files to set path, although thinking about it using shift key to multi select will do similar.

Normally I open the highest level assy like you suggest.

KENAT,

Have you reminded yourself of faq731-376 recently, or taken a look at posting policies:

http://eng-tips.com/market.cfm?

 

[karmoh]

Hi guys

I tend to use both methods. I have my own small design consultancy and depending on the project I will use typically use the following

On an electronics style cabinet or chassis assembly I will use one large folder with standard parts and fixtures and proprietary items in separate folders.

But when working on a large institutional project (Prison door and windows) I have all Jambs and mullions etc in their own respective folder, but only for that particular assembly. I can then use Rev-Man to copy and rename any particular part, sub-assy and assy to a new assembly folder. Rev-Man is a very powerful tool once you get to know its idiosyncrasies, saves a tremendous amount of time and worry.

I think that makes sense!!

To summarize I used what method seems logical for that particular project.

 

[beachcomber]

Kenat,
I see what you mean - I hadn't really taken into account that each sub-assy was to go in it's own folder.

bc.
2.4GHz Core2 Quad, 4GB RAM,
Quadro FX4600.