Damion Bartkowski wrote:
I have tried pack and go to assembly 2's folder with new names, but im not sure this will allow me to modify them without changing their originals in assembly 1.
Yes, Pack and Go, re-naming all files as part of the process, should remove all links to the original files. Just make sure you close them all before editing the new files. (I know this because I've forgotten to do that a few times.)
Rename the files per Glenn Schroeder comment - also what I started doing is saving the pack & go file on my desktop - just to make sure that all references are broken from the original file, most times if you save in the source folder the references could or can reconnect and make issues down the road.
I'm unclear if you want to alter the components or just their mates and relations.
I do not alter parts, because as an OEM, we buy them not make them. So, most components are referenced from the design library and remain fairly static. To perpetuate a cluster of components between assemblies without cross-reference, I open assembly 1, put the components into a folder together if they aren't already, convert these parts to a subassembly, and save the assembly externally to a file. Then I close assembly 1 without saving. Insert the saved subassembly into assembly 2, and dissolve it if subassembly status is troublesome. Then I can alter its mates in assembly 2 without affecting assembly 1, and vice-versa. I'll do this when we have a custom arrangement which needs 'copied' across similar systems within a project, and typically have a project subdirectory file location for non-library components and supporting files.
If altering components as well, P&Go as described will keep things more independent.
As you begin opening the new files using the File / Open dialog, be sure to click on the "References" button for each file and confirm any references are pointing where expected. If not, edit the references, open the file, and save to capture the new references.