change address of a sub assembly

[malf]

I can easily see (right- >property of the component-> pattern document path) what is the path of a sub assembly in the windows file system.
but if I wanted to change this path, to point, maybe, to a copy in different position, how could I do?
in practice as when solidworks at the opening does not find a subassembly and asks to find the new position.

 

[SimoneCRV]

right button on the sub assembly and replace component

 

[malf]

I had tried this system, but I think it's more for a real replacement, that is, one part with another. However it does not work as I would like, for example the most macroscopic problem is that it replaces the assembly, but not all its components that still go to the old position.

for now I do so: I change the name to the folder to the old position of the sub with closed solidworks, the reopening no longer finds the file and asks me to indicate the location and, at this point, I give the new location and I run the switch. It's a workaround that doesn't seem so dignified.

I think I saw, once, that there was a project file tree manager, like an external solidworks app. .

 

[malf]

this indication would seem promising, in the properties of the component. But I can't understand if it refers to the "replace component" command indicated by simone, or is a reference to another command

 

[drake]

hi... try to see if with the outside utility treehouse you can solve.

 

[SimoneCRV]

I had tried this system, but I think it's more for a real replacement, that is, one part with another. However it does not work as I would like, for example the most macroscopic problem is that it replaces the assembly, but not all its components that still go to the old position.

for now I do so: I change the name to the folder to the old position of the sub with closed solidworks, the reopening no longer finds the file and asks me to indicate the location and, at this point, I give the new location and I run the switch. It's a workaround that doesn't seem so dignified.

I think I saw, once, that there was a project file tree manager, like an external solidworks app. .

does not work as you want because you do not use it properly.
If the subassembly you go to replace, it has in the belly of the files that refer to other addresses you do not want, it is not solid fault, but how you built the subassembly in question.

 

[malf]

does not work as you want because you do not use it properly.
If the subassembly you go to replace, it has in the belly of the files that refer to other addresses you do not want, it is not solid fault, but how you built the subassembly in question.

the subassembly opening it by itself works properly. has its components open from the congruent position in the file system. when instead use as the object of a replacement is instead used only as assembly, continuing to use the components of what I am replacing. I don't think there's any guilt, but just figure out how it works.

 

[MassiVonWeizen]

solidworks loads as priority files already open.
if you have opened an alpha file with x address and open a beta set that contains alpha that has address y the axieme will load alpha/x because being already open it considers them priority than that stored alpha/y.
so if you replace a subaxieme with another and have shared files will also be loaded into the new subaxieme files and respective address already open.
is a very important concept in managing solidworks files, especially if you have multiple files with the same name in different folders.

to replace the subaxieme without incurring in this problem I must replace it without opening anything; by opening from solidworks to the bottom right there is the reference button, from here you give the new file paths

 

[malf]

to replace the subaxieme without incurring in this problem I must replace it without opening anything; by opening from solidworks to the bottom right there is the reference button, from here you give the new file paths

Thank you! This is a super advice. I had never seen this chance. It also seems very useful to check whether in the assembly that is opening, possibly, there are references to old folders or other.

 

[malf]

hi... try to see if with the outside utility treehouse you can solve.

no, unfortunately it seems that of a sub assembly or part I can only see the path of the file and not change it. instead this treehouse app seems very efficient to assign properties to various elements of a assembly, type part code or material

 

[MassiVonWeizen]

references should always be checked if you have a management with ambiguous files (the same file on multiple projects or same name in multiple folders) or work with external references.
if the list of files is long it can be useful to copy and paste everything into excel and with filters or functions verify fastmethyst all

 

[MassiVonWeizen]

to verify at any time the references just go to menu files> references

 

[drake]

I think this....it's true that sw allows you to manage and possibly change references to components, but it should still be an opportunity to use just in case of exceptional need. From my point of view it is necessary to change working methodology that allows you not to incur in these situations, which could lead to errors.