New Assy. refers back to old assy. while using Pack & Go 2

[Ripper2009]

Hello all. Friday...

A new assembly was created from an old assembly for various reasons.
When Pack & Go is used to send new assy, when unpacked, somehjow the files, etc refer to the OLD assembly not the new assembly.

What am I doing wrong?

Thanks in advance

Thanks,

Rip


SolidWorks 2007
SP 4.0

 

[Theophilus]

What is it you're doing? When I do this, I open a top-level assembly to copy my files to a new directory. All part and assembly files used in the top-level assembly are copied to the new directory. Other parts are not.

Is this what you're trying to do with Pack & Go?



Jeff Mowry

http://www.industrialdesignhaus.com

Reason trumps all. And awe transcends reason.

 

[msjames1]

Open the new assembly and hit "rebuild". The new part/subassembies should appear in the model tree.

 

[MDGroup]

Ripper,

This happens to me from time to time. Here's what my problem usually is, maybe yours is similar.

I have 'Part 1' in 'Assy A'. Somewhere there is a point, line, constraint, reference, etc that is somehow referenced to 'Assy A'.

Now, if I 'save-as' the entire assy as 'Assy B', 'Part 1' still needs to look into 'Assy A' to find that reference and re-build properly. So, if I pack-and-go the new assy, it also includes 'Assy A' so that it can re-build that one part.

My solution has been to look at any external references in each of the parts, find which is still pointing to the old assy, and update it to remove the reference or point to the new assy.

Hope this helps.

 

[Theophilus]

None of these problems ever happen to me like this, but I think I might know why--I do this process within SolidWorks with the top-level assembly open at the time. I'm thinking the method you are discussing is through Explorer and right-clicking to do the operation (right)?

My way stems from before SW had the Pack & Go feature and the process was called "find references" to copy (or move) files someplace else. Anyway, I think this method dodges the problems of disoriented references because the references are in order when the assembly is open and the files are copied (since they reside only in that assembly--for the purposes of this discussion).



Jeff Mowry

http://www.industrialdesignhaus.com

Reason trumps all. And awe transcends reason.

 

[Ripper2009]

Wow...loads of info!!!
Thanks to all..I'll try the fixes out....

Later..

Thanks,

Rip


SolidWorks 2007
SP 4.0