management of assemblies

[d400]

Hello, I have just written but I have always read this forum !!!
Congratulations to all those who make their experience available to new users of the sw.
So let us come to my question:
design more parts than save with *.ipt;
assemble a set that saves with *.iam;
My problem is about encoding parts.. .
In practice for every "project/work" I create a sub-folder "welded constituents" in which I go to insert the various *.ipts that make up the axieme, this to separate the generic *.ipts from those, precisely, which are part of a set.
in the case if the axieme is called pippo.iam the parts will be pippo_1.ipt...pippo2_ipt etc...
I ask you at this point... how do you manage the individual parts of a set?
With the increase of the projects in fact this way seems to me to bring me to a little confusion!!
Thank you.

 

[stefanobruno]

I ask you at this point... how do you manage the individual parts of a set?
With the increase of the projects in fact this way seems to me to bring me to a little confusion!!
Thank you.

Welcome.
I manage my welded components, leaving them all in the same sales folder, along with the overall welded and unwelded components.
the distinction is made with a suffix, letter or number dependent on the complexity of the welded.
work for different realities and all do so, who prefers letters, who numbers but all hold files together in the same folder.
the important is to give a coherent coding, not pippo_1 or pluto_2 as often seen in autocad blocks:biggrin:

Bye.

 

[d400]

Welcome.
I manage my welded components, leaving them all in the same sales folder, along with the overall welded and unwelded components.
the distinction is made with a suffix, letter or number dependent on the complexity of the welded.
work for different realities and all do so, who prefers letters, who numbers but all hold files together in the same folder.
the important is to give a coherent coding, not pippo_1 or pluto_2 as often seen in autocad blocks:biggrin:

Bye.

Hello and thank you...
pippo or pluto..mai sia !!!
of course the name is consistent with our internal coding...that's changing to identify the components of a set is only the "_x" etc...
So there's no alternative?
Hi.

 

[stefanobruno]

So there's no alternative?

That doesn't sound dramatic.
and look at me as a piss:biggrin:

 

[Catafratto]

I've done some experiments, but in the end a good progressive takes away many headaches! here, if it can help you, as I make many pieces dx and sx I call them pippo.0001.01 (sx) and pippo.0001.02 (dx), taking care that pippo.0001.01 is always the father and pippo.0001.02 always the mirrored (or derived) so to find everything immediately. . .

 

[d400]

I've done some experiments, but in the end a good progressive takes away many headaches! here, if it can help you, as I make many pieces dx and sx I call them pippo.0001.01 (sx) and pippo.0001.02 (dx), taking care that pippo.0001.01 is always the father and pippo.0001.02 always the mirrored (or derived) so to find everything immediately. . .

So let's all do this!
the problem...or false problem... is when you make me use of a new part and some already used.
e.g.
a tie made with a cross and side wings.
If I make another one where I want to change the cross and keep the wings to whom I refer?
This is the hippo I find!!!