I have an assembly with virtual parts defined in context. I use this assembly as a template for generating new assemblies. To do this, I copy tree the assembly and parts I want to make new versions of. The virtual parts saved in the assembly must be copied when the top level assembly is copied, so there is a new copy of them each time. This is good, they are vitual and exist only in the assembly. But when I copy, even though there is a new part defined in the new assembly, showing in the feature tree as being a virtual component in the current assemlby, it is now out of context. For some reason even though both the part and assembly are copied, the part remains defined in the context of the original assembly.

So, I have Assembly A with virtial component:

Part^A->

and copy it. Now I have Assembly B with virtual component:

Part^B->?

where Part^B is defined in context of Assembly A and now out of context.

I don't understand how a virtual part can be defined in an assembly where it does not exit.

I could to an open with references on the part to fix it if it was a normal part, but it's virtual, so I can't open it at all except from the assembly.

How do I repair the references, or keep it from doing this when I copy tree?

-Thanks

Thomas