AnsweredAssumed Answered

Moving lots of assemblies

Question asked by Eric Snyder on Sep 20, 2010
Latest reply on Sep 21, 2010 by Kelvin Lamport

Like • Show 0 Likes0
Comment • 7

I have the following file structure:

Main tool folder

| ---Tool #1

|---Various folders

|---Tool #1 Tooling folder

| ------Part 1

| ------Part 2

| ------Assembly

|---Tool #2

|---Tool #3

...

|---Tool #492

The issue is that the main tool folder is getting too full. I would like to organize the tools into tool files holding #1 - #99, #100 - #199, etc. The real issue is that if I move the assemblies then all the references will break. Loading each assembly and using pack and go seems like a real chore.

How can this be accomplished in a fairly simple way?

No one else has this question

Outcomes

Brian Lindahl Sep 20, 2010 6:32 PM

Can you write a macro? If so, investigate the SWDocManager to replace the external reference in the files after/when you move them. You need to request a "key" from SW API support team to use the SWDocManager, but the key is free. I've done some stuff with the DocManager, and it is pretty quick with what it does. Way quicker than opening in SW and doing the same stuff, and in your case, way quicker than fixing broken file references.

Actions

Kelvin Lamport Sep 20, 2010 8:34 PM

References will only be broken if parts from one grouping reference parts from another grouping. Is that the case?

Actions

Eric Snyder @ Kelvin Lamport on Sep 21, 2010 9:14 AM

Kevin:

You are correct. I can move the entire part folder and as long as all the components are in that folder. I just tested that and it worked.

I do have some assemblies that have components that are outside of that folder. What to do on those? Can I move the entire folder with SW explorer?

Actions

Scott McFadden @ Eric Snyder on Sep 21, 2010 9:39 AM

Eric,

You wouldn't happen to have PDM would you?

This could be accomplished fairly easily inside of the vault.

Other then that I would use Solidworks Explorer.

Actions

David Oustifine @ Eric Snyder on Sep 21, 2010 12:29 PM

Just make sure the paths are added to your "reference documents" list in SW.

Go to TOOLS>OPTIONS>FILE LOCATIONS>REFERENCE DOCUMENTS and add all the paths to this list (assuming you don't have duplicate file names).

Then it wont matter where you move them to so long as that new location is added the reference documents path list prior to opening the assembly.

Actions

Anna Wood @ Eric Snyder on Sep 21, 2010 12:34 PM

When the message pops up that it can't find a file just go look for it. If you know where the files are you can search for it to re-link it up. With a consistent file and folder naming convention and no files named the same it is pretty easy to do. We do this all the time with our projects.

Actions

Kelvin Lamport @ Eric Snyder on Sep 21, 2010 12:57 PM

Unfortunately, SW Explorer has no Move option. Only Open, P&G, Rename, and Replace.

If the referenced components are in one of the other moved groupings, you may have to bite the bullet and re-reference manually. The File > Open > References method is probably one of the easiest methods for that ... or the SW Explorer > Replace option (although I've never tried that one).

Actions

7 Replies

Brian Lindahl Sep 20, 2010 6:32 PM
Mark Correct
Correct Answer
Can you write a macro? If so, investigate the SWDocManager to replace the external reference in the files after/when you move them. You need to request a "key" from SW API support team to use the SWDocManager, but the key is free. I've done some stuff with the DocManager, and it is pretty quick with what it does. Way quicker than opening in SW and doing the same stuff, and in your case, way quicker than fixing broken file references.
Like • Show 0 Likes0
Actions
Kelvin Lamport Sep 20, 2010 8:34 PM
Mark Correct
Correct Answer
References will only be broken if parts from one grouping reference parts from another grouping. Is that the case?
Like • Show 0 Likes0
Actions
- Eric Snyder @ Kelvin Lamport on Sep 21, 2010 9:14 AM
  Mark Correct
  Correct Answer
  Kevin:
  
  You are correct. I can move the entire part folder and as long as all the components are in that folder. I just tested that and it worked.
  
  I do have some assemblies that have components that are outside of that folder. What to do on those? Can I move the entire folder with SW explorer?
  Like • Show 0 Likes0
  Actions
  - Scott McFadden @ Eric Snyder on Sep 21, 2010 9:39 AM
    Mark Correct
    Correct Answer
    Eric,
    You wouldn't happen to have PDM would you?
    This could be accomplished fairly easily inside of the vault.
    Other then that I would use Solidworks Explorer.
    Like • Show 0 Likes0
    Actions
  - David Oustifine @ Eric Snyder on Sep 21, 2010 12:29 PM
    Mark Correct
    Correct Answer
    Just make sure the paths are added to your "reference documents" list in SW.
    Go to TOOLS>OPTIONS>FILE LOCATIONS>REFERENCE DOCUMENTS and add all the paths to this list (assuming you don't have duplicate file names).
    Then it wont matter where you move them to so long as that new location is added the reference documents path list prior to opening the assembly.
    Like • Show 0 Likes0
    Actions
  - Anna Wood @ Eric Snyder on Sep 21, 2010 12:34 PM
    Mark Correct
    Correct Answer
    When the message pops up that it can't find a file just go look for it. If you know where the files are you can search for it to re-link it up. With a consistent file and folder naming convention and no files named the same it is pretty easy to do. We do this all the time with our projects.
    Like • Show 0 Likes0
    Actions
  - Kelvin Lamport @ Eric Snyder on Sep 21, 2010 12:57 PM
    Mark Correct
    Correct Answer
    Unfortunately, SW Explorer has no Move option. Only Open, P&G, Rename, and Replace.
    
    If the referenced components are in one of the other moved groupings, you may have to bite the bullet and re-reference manually. The File > Open > References method is probably one of the easiest methods for that ... or the SW Explorer > Replace option (although I've never tried that one).
    Like • Show 0 Likes0
    Actions

Moving lots of assemblies

Outcomes

Related Content

Recommended Content