Problem with Renaming Content Center parts

[Anonymous]

I have a weldment assembly that is made up of W-Flanges from the Content Center. Most of these W-Flanges feature copes or special cuts at one end or another. So they need a discreet part number in order to keep track of them. At first the Content Center seemed like a Godsend due to the ease of use. The problem arose when I attempted to rename these Content Center Parts.

The typical procedure that I use when building such an elaborate assembly is flesh out the design, get it finalized (somewhat), and then rename the parts to dash numbers of the original assembly. For example, the assembly is called “6015-015.iam”. The filename for the first second and third parts in this assembly are 6015-015-01.ipt, 6015-015-02 ipt, and 6015-015-03 ipt. I find this naming convention particularly useful when viewing a file list of a directory. Without much effort you can identify which files that belong to a particular assembly.

However, the problem arose after I needed to rename several of the parts from the content center. I would open the assembly and select a component. I would then open the component, save as a new name and then close the file. Back in the assembly, I would then replace the old component with the one I renamed (I realize that this is a long hand way of doing this, and that there is an easier way through the Vault. But it suits the purposes of the discussion).

When I “Save as” with a part from the Content Center, it acts like the operation worked. There is even a new file made which can be seen in the browser. However when you go to use this file in your assembly, it inserts the OLD Content Center File! Attempting to open the new filename yields even stranger results. When you open the new file, the OLD file opens instead. No amount of computer gymnastics using Windows Explorer or File manager can circumvent this issue. Believe me, I tried.

So I have a large assembly that has several dozen parts with file names that do not comply with company standards (as well as my own) and that I cannot rename. How can I remedy this? Until I get around this issue, I have advised other users in my group to not use ANY files form the Content Center.

Thank You,
Dominic Greco

[Anonymous]

I have done that many times and have no problems. You must be doing
something incorrectly. (There are other reasons one might come up with to
be "scared" of CC parts but this is not one of them.) I don't typically use
weldments but have done this many times with regular assemblies without
problems. The browser tree will still often show the old filename even
though the new ones is being used. Simply open the part up to see that it
is indeed the right part. (You can even use the assembly tool : "Rename
Browser Nodes" to overcome this.)

--
Rob
Inventor 2008 SP2
Vault 2008 SP1
ATI FireGL X2 AGP Pro
Graphics Driver: 8.223.0.0
(2 Monitors at 1280x1024)
Using Direct 3D
Intel Pentium 4 CPU 2.40 GHz
2.00GB of RAM


wrote in message news:5852116@discussion.autodesk.com...
I have a weldment assembly that is made up of W-Flanges from the Content
Center. Most of these W-Flanges feature copes or special cuts at one end or
another. So they need a discreet part number in order to keep track of them.
At first the Content Center seemed like a Godsend due to the ease of use.
The problem arose when I attempted to rename these Content Center Parts.

The typical procedure that I use when building such an elaborate assembly is
flesh out the design, get it finalized (somewhat), and then rename the parts
to dash numbers of the original assembly. For example, the assembly is
called "6015-015.iam". The filename for the first second and third parts in
this assembly are 6015-015-01.ipt, 6015-015-02 ipt, and 6015-015-03 ipt. I
find this naming convention particularly useful when viewing a file list of
a directory. Without much effort you can identify which files that belong to
a particular assembly.

However, the problem arose after I needed to rename several of the parts
from the content center. I would open the assembly and select a component. I
would then open the component, save as a new name and then close the file.
Back in the assembly, I would then replace the old component with the one I
renamed (I realize that this is a long hand way of doing this, and that
there is an easier way through the Vault. But it suits the purposes of the
discussion).

When I "Save as" with a part from the Content Center, it acts like the
operation worked. There is even a new file made which can be seen in the
browser. However when you go to use this file in your assembly, it inserts
the OLD Content Center File! Attempting to open the new filename yields even
stranger results. When you open the new file, the OLD file opens instead. No
amount of computer gymnastics using Windows Explorer or File manager can
circumvent this issue. Believe me, I tried.

So I have a large assembly that has several dozen parts with file names that
do not comply with company standards (as well as my own) and that I cannot
rename. How can I remedy this? Until I get around this issue, I have advised
other users in my group to not use ANY files form the Content Center.

Thank You,
Dominic Greco

[Anonymous]

You might consider the "Frame Generator", it will give you descreet file
names for each member even if they are all identical. The miter & notch will
be easier for fitting. Can also be used as a weldment.

--
Dell 670 dual Xeon - 3.2
3gb memory, SCSI320-15k
XP-Pro, sp2
Quadro FX3400: Driver: 169.61 Direct3D
IV2008-pro sp2,
SpacePilot Rel V: 3.5.4 Dvr V: 6.4.4 Firmware 3.12

"RobV" wrote in message
news:5852192@discussion.autodesk.com...
I have done that many times and have no problems. You must be doing
something incorrectly. (There are other reasons one might come up with to
be "scared" of CC parts but this is not one of them.) I don't typically use
weldments but have done this many times with regular assemblies without
problems. The browser tree will still often show the old filename even
though the new ones is being used. Simply open the part up to see that it
is indeed the right part. (You can even use the assembly tool : "Rename
Browser Nodes" to overcome this.)

--
Rob
Inventor 2008 SP2
Vault 2008 SP1
ATI FireGL X2 AGP Pro
Graphics Driver: 8.223.0.0
(2 Monitors at 1280x1024)
Using Direct 3D
Intel Pentium 4 CPU 2.40 GHz
2.00GB of RAM


wrote in message news:5852116@discussion.autodesk.com...
I have a weldment assembly that is made up of W-Flanges from the Content
Center. Most of these W-Flanges feature copes or special cuts at one end or
another. So they need a discreet part number in order to keep track of them.
At first the Content Center seemed like a Godsend due to the ease of use.
The problem arose when I attempted to rename these Content Center Parts.

The typical procedure that I use when building such an elaborate assembly is
flesh out the design, get it finalized (somewhat), and then rename the parts
to dash numbers of the original assembly. For example, the assembly is
called "6015-015.iam". The filename for the first second and third parts in
this assembly are 6015-015-01.ipt, 6015-015-02 ipt, and 6015-015-03 ipt. I
find this naming convention particularly useful when viewing a file list of
a directory. Without much effort you can identify which files that belong to
a particular assembly.

However, the problem arose after I needed to rename several of the parts
from the content center. I would open the assembly and select a component. I
would then open the component, save as a new name and then close the file.
Back in the assembly, I would then replace the old component with the one I
renamed (I realize that this is a long hand way of doing this, and that
there is an easier way through the Vault. But it suits the purposes of the
discussion).

When I "Save as" with a part from the Content Center, it acts like the
operation worked. There is even a new file made which can be seen in the
browser. However when you go to use this file in your assembly, it inserts
the OLD Content Center File! Attempting to open the new filename yields even
stranger results. When you open the new file, the OLD file opens instead. No
amount of computer gymnastics using Windows Explorer or File manager can
circumvent this issue. Believe me, I tried.

So I have a large assembly that has several dozen parts with file names that
do not comply with company standards (as well as my own) and that I cannot
rename. How can I remedy this? Until I get around this issue, I have advised
other users in my group to not use ANY files form the Content Center.

Thank You,
Dominic Greco