problema "save-as" family table wf5.0

[marco1874]

hello to all, I'm working on an "immmmmense" project where a basic machine was created assembled to modules (all fathers of family table ) and now I have inserted the duplication to popular the range . the range consists of twenty different sizes between them for size and powers. It is cold machines.

Today, by magic, during a normal operation of "saving by name" the pro-e gives me a mistake that prevents me from saving.

The operations I do are:

1) I choose the father and all ft filgi to duplicate
2) Apply new codes with the right extensions
3) click on advanced
4) I say in which assemblies I will replace old codes with new ones in creation
5) the pro-e tells me "not all members of the family table are available with the same update request "

A colleague does it and it doesn't change.

the father of ft is verified, in check-out and regenerated with green light.

If any of you have any right, I'd be grateful.

Thank you and hello.

 

[Alberto.E]

hi, from experience I never use the save as but rename. I know it's a workmanship but you should open in session all the fathers and family tables and assemblies where you have to do replacements and begin rename in session. so you're sure you don't have any mistakes.

 

[zilioalex]

Hello marco1874,

the function you explain is very interesting for the management of the rename of family table instances, but I did not understand how to use it.

I have the wf5 and I would like, as you say, to rename the instances and replace them together without having to open everything in memory.

Can you explain?

grits 1000

 

[DANI-3D]

Bye.
I also recommend rename. if I can do the rename in session to get a new code, otherwise I will cover the project in a new folder I open it and rename it, at the end the new codes that have general moved them to the various workbooks and the support folder with the unvaried codes the gate.

 

[bologna1]

Hi.
I have yet to study the wf5 and try to put me in this discussion.

I know that you with the save-as create of new fathers and new instances, but in this way there is the risk of duplicating requests with the same name within two fathers, probably, the instances that do not remove within the family the program recognizes them as two equal prts and does not make you proceed.

for rhinos in session is another system but it is a great job if the axieme is immense.

I would be more for a backup in a folder and then rename.

a pdm would solve many things you might consider buying