MimiN63
Mechanical
- Oct 31, 2003
- 45
I am trying to “save-as” a top-level assembly containing route subassemblies, but cannot successfully do so. This is what I’ve done:
1. In PDMWorks, I copy a project that contains the top assy, route sub-assy’s, & their parts. All files names contain a common phrase, so I change the filenames using the “replace text” function in PDM.
2. The original project had also contained some blank .sldprt and .sldasm files, equal to the number of route assy’s & parts in the original assembly. They, too, are renamed during step 1.
3. After copying the project, I checked out the new top-level assembly and all children (but did not open).
4. I opened the original top-level assembly (read-only) and did a “save-as” to the new files, including the route subassemblies and parts through the references dialogue box (using the blank files to get the new filenames).
I had the following problems:
1. When using “copy project” and “replace text” in PDMWorks, it did not rename the route subassemblies or their children. They are just links.
2. Problems maintaining the in-context relationships of the top-level assy & the route files after they were copied.
3. After picking new files for the route assemblies and their parts in the references dialog box and saving, the new assembly referenced the correct route subassemblies, but was still referencing the old route parts.
4. PDMWorks said that I owned and had checked out all of the new project’s files. But the SW references box said that a couple of the route parts were read-only. They are clearly owned by me in PDMWorks.
I have played with this off and on for the past month or so, tying different ways to make this work. But something is always off. If anyone has had similar experiences or just has some suggestions, I would be grateful to hear them.
MimiN
1. In PDMWorks, I copy a project that contains the top assy, route sub-assy’s, & their parts. All files names contain a common phrase, so I change the filenames using the “replace text” function in PDM.
2. The original project had also contained some blank .sldprt and .sldasm files, equal to the number of route assy’s & parts in the original assembly. They, too, are renamed during step 1.
3. After copying the project, I checked out the new top-level assembly and all children (but did not open).
4. I opened the original top-level assembly (read-only) and did a “save-as” to the new files, including the route subassemblies and parts through the references dialogue box (using the blank files to get the new filenames).
I had the following problems:
1. When using “copy project” and “replace text” in PDMWorks, it did not rename the route subassemblies or their children. They are just links.
2. Problems maintaining the in-context relationships of the top-level assy & the route files after they were copied.
3. After picking new files for the route assemblies and their parts in the references dialog box and saving, the new assembly referenced the correct route subassemblies, but was still referencing the old route parts.
4. PDMWorks said that I owned and had checked out all of the new project’s files. But the SW references box said that a couple of the route parts were read-only. They are clearly owned by me in PDMWorks.
I have played with this off and on for the past month or so, tying different ways to make this work. But something is always off. If anyone has had similar experiences or just has some suggestions, I would be grateful to hear them.
MimiN