Accepted Solutions
This appears to be PTC changing the UI from existing standards. Is this screen shot from Creo 9? I have not installed Creo 9 yet but I think this is just a change of label in the UI. It appears they made a UI change and did not update the documentation (poor form but increasingly common). The Creo 9 help files list the options as follows for merge/inheritance:
If you were in assembly mode when you captured the screenshot then I would speculate the below information applies:
An external inheritance establishes a direct reference between parts. A local inheritance will create the feature in the context of an assembly (the assembly will be a parent of the target model of the inheritance).
Use an external version unless design intent requires that it be done using an assembly. This will minimize external references.
Use this link to find an article on Inheritance features:
Scroll down to my response containing the zip file. There is a section on the use case for as cast and as machined models.
This appears to be PTC changing the UI from existing standards. Is this screen shot from Creo 9? I have not installed Creo 9 yet but I think this is just a change of label in the UI. It appears they made a UI change and did not update the documentation (poor form but increasingly common). The Creo 9 help files list the options as follows for merge/inheritance:
If you were in assembly mode when you captured the screenshot then I would speculate the below information applies:
An external inheritance establishes a direct reference between parts. A local inheritance will create the feature in the context of an assembly (the assembly will be a parent of the target model of the inheritance).
Use an external version unless design intent requires that it be done using an assembly. This will minimize external references.
Use this link to find an article on Inheritance features:
Scroll down to my response containing the zip file. There is a section on the use case for as cast and as machined models.
