That is what I was afraid you were talking about. When demoting a pattern there are three things that I don't like about it. First of all it looses my constraints that I had already took the time to define. Secondly, it then makes the pattern an assembly. This seems to me a bit ridiculous. If I want to Pattern a Pattern of hardware, it seems silly that I have to have an assembly of just hardware. I don't want to end up with thousands of assemblies of just hardware. Thirdly, and most importantly, I now loose the whole purpose of what Patterns are created for. The nice thing about Patterns is this. If I create a hole pattern and then pattern hardware to that hole pattern. If by chance I have to change the hole pattern distances, my hardware updates with it. Once you use the Demote command, it makes it an assembly, and the original pattern is no longer existent so it does not update and you would have to go into the assembly and change the distance between the components. Oh wait 😞 you can't because if you open the assembly, there is no dimension between the parts. It is just based on what it was at that point in time. So then you basically have to start over creating your first pattern, demoting and then creating your second pattern. So you see really you are not at all doing what this thread topic is asking. You are not making a Pattern of a Pattern. Instead you are replacing one Pattern with another, that no longer updates. This does not seem like an acceptable practice to me. Does anyone else have any ideas of a better way to do this same concept?
