I work at a company where we build up assemblies that often
need aname change in the middle of the project. Usually, this
meansswapping out a prefix in the name of the assembly and 90% of
itscomponents (all components except the design librarycomponents).
We've been using Pack and Go to accomplish this. We check out theold assembly, run Pack and Go, and then check in the newly namedassembly in PDMWorks. The problems occur when we then try to checkout the new assemblies. All of the design library components aresuddenly unresolved and we need to point to the path of eachcomponent in the new assembly.
Question 1 to the forum: Am I doing something wrong? Does it matterif I check or uncheck the library components when running Pack andGo? They don't get renamed anyway...
Question 2 to the forum: Are there any "Best Practice"methods/ideas/random musings for using PDMWorks to manageassemblies that need to be renamed en masse (excepting designlibrary)?
We are working with SW2007 SP5
We've been using Pack and Go to accomplish this. We check out theold assembly, run Pack and Go, and then check in the newly namedassembly in PDMWorks. The problems occur when we then try to checkout the new assemblies. All of the design library components aresuddenly unresolved and we need to point to the path of eachcomponent in the new assembly.
Question 1 to the forum: Am I doing something wrong? Does it matterif I check or uncheck the library components when running Pack andGo? They don't get renamed anyway...
Question 2 to the forum: Are there any "Best Practice"methods/ideas/random musings for using PDMWorks to manageassemblies that need to be renamed en masse (excepting designlibrary)?
We are working with SW2007 SP5
After the pack and go, with the library components checked (to anew folder), SolidWorks has no trouble finding the design librarycomponents (as expected--they are copied into the new folder).However, after a check in, and then a check-out to a new folder,SolidWorks can't find the library components if they have beendeleted from the folder to which they were copied. It is likePDMWorks gets a brain fart and can't figure out that thesecomponents can be found in the design library. The probable reasonfor the brain fart is that the assembly thinks that the referencedparts are still located in the folder to which all parts werecopied.
I have now tested the behavior when the design library componentsare unchecked in the Pack and Go dialog. There is no problemopening the assembly in the new folder, and the Design Librarycomponents are fetched from S:. I think that this is the solutionto our problem, when the components are checked, the Assembly wantsto look for them in their copied location. The assembly thenmaintains this "desire" after a check-in/out cycle eventhough PDMWorks has a good idea of where these parts arelocated.
Here is what the help says about the check box for pack and go
Select or clear check boxes to include files in the saved folder orzip file.
That's it...