#2 & #3 has me a little curious. I’m trying to see it from your viewpoint, so bear with me here. You said:
2. I SPECIFICALLY don’t want a part changed in the drawing. If I could I would restrict changes (after release) to be done in assembly so the actual impact of your change could be seen. Actually, I wouldn’t go quite that far, but the principle remains. I don’t want parts changed in the drawing.
a. Is your system set up that a user could open the drawing and make modifications that would propagate into the model (due to life cycle state) but that user couldn’t simply open the model and make modifications there? If both the drawing and the model are released, they cannot change it anyway (except locally). If it’s at some sort of In Work state, that user could simply open the model and make the change after finding out it’s a created dimension.
b. Also, even in drawing mode the process of modifying a shown dimension is a deliberate act. Unless I’m missing something, this is not an act that someone can stumble through to accidentally change the model from the drawing interface: double click shown dimension > pick ‘Nominal Value’ cell for dimension value > enter new value > pick OK button > regenerate. (Alternately: single click shown dimension > RMB > Modify Nominal Value > enter new value > Enter key > regenerate.) If someone is claiming they’re accidentally modifying a shown dimension they’re shoveling a lot of BS.
3. You’re right, but again, if I use FRONT, TOP and RIGHT that isn’t a problem. Also, your assumption is that whoever changes the model after me is less skilled than I am and doesn’t see that change.
a. You reference everything to FRONT, TOP AND RIGHT instead of referencing everything to set datums? So when someone wants to change the distance from [-A-] displayed as a created dimension they have calculate the difference, go into the model, find a different dimension and apply that difference? Somehow I feel that I’m reading this explanation as a good thing yet I can’t figure out how it is a good thing.
b. Yes, always assume the next user will struggle unless it is the most straight-forward methodology possible. Actually, even then.