DA question

[Anonymous]

I, sometimes, need to copy a library part or assembly in DA. For some reason
this can't be done. Is there something I'm missing and if not does anyone
understand the logic behind this limitation?

Thanks,
Matt

[Anonymous]

Parts in a library path in a project file are treated as read-only
whether in IV of DA. You will need a project file with the library
parts in workgroup paths. If you are using semi-isolated for
multi-user, you must turn it off to use DA. This is because of the
check-in/check-out procedure in semi-isolated.


Matt Hendey wrote:
> I, sometimes, need to copy a library part or assembly in DA. For some reason
> this can't be done. Is there something I'm missing and if not does anyone
> understand the logic behind this limitation?
>
> Thanks,
> Matt
>
>
>

--
Hal Gwin
Mechanical Designer
Xenogen

W2K SP4
Dell Precision 650
Dual 2.66 GHz Xeon
1.5 GB DDR
Quadro4 900 XGL
nVidia 6.14.10.4472 w/registry update
Dell UltraSharp 19" LCD

[Anonymous]

What I don't understand is if you can do a Save As in Inventor with library
parts and assemblies way can't you do it in DA. Same program with a
different GUI, correct?

I guess this would be considered a wish item.

Matt

[Anonymous]

Savecopyas merely makes a copy of a file with a new name, it does not
change file linking in the case of assemblies. While you can do a
Savecopyas on library parts in IV, you cannot edit the library part.
With DA you would be working from an assembly and renaming, and possibly
relocating, a sub-part/assembly. This would constitute changing the
assembly you are working on, something not allowed with library
parts/assemblies. Not the same as copying and renaming a part/assembly.

Matt Hendey wrote:

> What I don't understand is if you can do a Save As in Inventor with library
> parts and assemblies way can't you do it in DA. Same program with a
> different GUI, correct?
>
> I guess this would be considered a wish item.
>
> Matt
>
>
>

--
Hal Gwin
Mechanical Designer
Xenogen

W2K SP4
Dell Precision 650
Dual 2.66 GHz Xeon
1.5 GB DDR
Quadro4 900 XGL
nVidia 6.14.10.4472 w/registry update
Dell UltraSharp 19" LCD

[Anonymous]

Correct. Changing the link information in a library IAM file would be
breaking the rules but, if I'm copying a project and I want to copy a
library part with it, it would be nothing more then a save as. Correct?

Matt

"Hal Gwin" wrote in message
news:BDE56E37932DB3006A04F9EA21DF2ED2@in.WebX.maYIadrTaRb...
> Savecopyas merely makes a copy of a file with a new name, it does not
> change file linking in the case of assemblies. While you can do a
> Savecopyas on library parts in IV, you cannot edit the library part.
> With DA you would be working from an assembly and renaming, and possibly
> relocating, a sub-part/assembly. This would constitute changing the
> assembly you are working on, something not allowed with library
> parts/assemblies. Not the same as copying and renaming a part/assembly.
>
> Matt Hendey wrote:
>
> > What I don't understand is if you can do a Save As in Inventor with
library
> > parts and assemblies way can't you do it in DA. Same program with a
> > different GUI, correct?
> >
> > I guess this would be considered a wish item.
> >
> > Matt
> >
> >
> >
>
> --
> Hal Gwin
> Mechanical Designer
> Xenogen
>
> W2K SP4
> Dell Precision 650
> Dual 2.66 GHz Xeon
> 1.5 GB DDR
> Quadro4 900 XGL
> nVidia 6.14.10.4472 w/registry update
> Dell UltraSharp 19" LCD
>

[Anonymous]

If it is a library part, why copy it? When you copy the assembly (with
a new name presumably), ignore the library part, the new assembly will
then resolve the library part in its original location.

Matt Hendey wrote:
> Correct. Changing the link information in a library IAM file would be
> breaking the rules but, if I'm copying a project and I want to copy a
> library part with it, it would be nothing more then a save as. Correct?
>
> Matt
>

--
Hal Gwin
Mechanical Designer
Xenogen

W2K SP4
Dell Precision 650
Dual 2.66 GHz Xeon
1.5 GB DDR
Quadro4 900 XGL
nVidia 6.14.10.4472 w/registry update
Dell UltraSharp 19" LCD

[Anonymous]

Most of my projects are tanks. The projects are small 25 to 100 parts. With
every new tank I try to find the closes tank that we have done already.
Sometimes this could be one of our standard tanks that have standard parts
(Library Parts) in them that will have to be modified to create the new
custom tank. When I DA the standard tank, from the IDW down, I will want to
copy that library part with the tank because I know it will be modified. But
I can't because it's a library part. So, I will continue to copy everything
else then when I open the new assembly I will save the library part as the
new non library part that will need to modified. Then I will replace the old
library part with the new custom part before it's modified so that I will be
able to retain all the constraints. After this I can then again open the new
non library part and make the desired changes.

This would be a lot simpler if I could have copied the library part over in
DA with the rest of the tank (project) in the beginning.

I'm not griping but the new, library, read only, functionality seams to be
more for the multi-user environment. I find that, so fare, it has not been
of any use to me as a single user. In fact it seams to make things a little
more difficult, and it does have some loop holes.

Thanks,
Matt

[Anonymous]

Have you tried creating a project file with the library paths as
workgroup paths, then create your tank project files and add the library
project file as the "included file" entry. this should allow you to
reference your libraries, open a library part and edit it whenever you
need to, and copy that file with the other project files in DA.


Matt Hendey wrote:

> Most of my projects are tanks. The projects are small 25 to 100 parts. With
> every new tank I try to find the closes tank that we have done already.
> Sometimes this could be one of our standard tanks that have standard parts
> (Library Parts) in them that will have to be modified to create the new
> custom tank. When I DA the standard tank, from the IDW down, I will want to
> copy that library part with the tank because I know it will be modified. But
> I can't because it's a library part. So, I will continue to copy everything
> else then when I open the new assembly I will save the library part as the
> new non library part that will need to modified. Then I will replace the old
> library part with the new custom part before it's modified so that I will be
> able to retain all the constraints. After this I can then again open the new
> non library part and make the desired changes.
>
> This would be a lot simpler if I could have copied the library part over in
> DA with the rest of the tank (project) in the beginning.
>
> I'm not griping but the new, library, read only, functionality seams to be
> more for the multi-user environment. I find that, so fare, it has not been
> of any use to me as a single user. In fact it seams to make things a little
> more difficult, and it does have some loop holes.
>
> Thanks,
> Matt
>
>
>

--
Hal Gwin
Mechanical Designer
Xenogen

W2K SP4
Dell Precision 650
Dual 2.66 GHz Xeon
1.5 GB DDR
Quadro4 900 XGL
nVidia 6.14.10.4472 w/registry update
Dell UltraSharp 19" LCD

[Anonymous]

You can copy a library part to another location in the project without
renaming. Select the action as copy and then RMB in the location box and
pick a new location. The only thing you can't do is rename right away.

Kathy Johnson

[Anonymous]

Ya, I could try that. My library paths are under my workgroup anyway so I
could just create another project with all the library paths deleted. It
will make library parts harder to see since I doubt that DA will show them
in darker gray boxes but if that's what it takes I may do that.

Thanks,
Matt

[Anonymous]

Are you sure. I have been able to select copy on Library parts but DA won't
let me make the change to the name.

Matt

[Anonymous]

You can't change the name. RMB on the action to copy. RMB on the File
Location to copy the file to another location outside the libarary. Save.
Then change the name of the copied file.

Kathy Johnson

[Anonymous]

Sorry I didn't catch on the first time. I have never tried that.

Thanks,
Kathy