if_goto

Hi Todd, can you give a little more information on what you're trying to do? Are you wanting to recall alignments before reporting certain features so that your datums are the measured value?

Yes, as I stated, I'm using a theoretical zero for OP1, but need to use the actual datums in OP2. To be more clear, the main datums will be machined in OP2. How can I set this up to report all the OP1 dimensions again, but using the actual datums, rather than theoretical?

Can you not just rerun the entire part when OP2 is done? 

Personally I would make two programs to prevent someone who is less adept from hitting continue and ramming my probes into solid metal. 

But why the combined program to begin with? 

I can, but as it is now, all the op1 dimensioning is to a theoretical zero. Even if I rerun the entire part, those features will still be dimensioned to the same theoretical alignments.

I suppose it could be done that way. I just thought it would be kind of inconvenient, but as it's turning out, not as inconvenient as trying to figure this out!

I suppose it could be done that way. I just thought it would be kind of inconvenient, but as it's turning out, not as inconvenient as trying to figure this out!

I see where you are going, you want to be be able to choose to use datum A (actual) or datum AA (fake) at will, based on the condition of the part. 
Maybe you could reach this point with some operator inputs and some variables, though I have never tried to use a variable in a datum assignment. In theory it shouldn't know the difference and just perform the calculations. However that would only work for GD&T, not any measured features. 

Or like BIGWIG7  said, just realign the part to the new features and hit update.
Though that process would work best if you made a copy of your code and then "updated" then pasted those new (and renamed) alignments/dimensions back into your original program. Then you could use your if_goto to skip to the end of the program and miss all those updated features.