Been looking at some code (some of the Pro2 triggers etc out of interest), where there are statements like "if 4 = 5 then", or "if yes = no then".
Can anyone shed any light on what the purpose of this sort of thing is? The then statement has code associated with it. Surely it would never run?
I've seen this before elsewhere if memory serves.
It could serve as a way of essentially commenting out code, while making sure it still compiles.
I sometimes use it to force transactions / scoping:
if FALSE then find first my_record.
Why you'd pick "4 = 5" or "yes = no" instead of simply using "FALSE" is probably a matter of personal taste or a method of making it easy to find with a Ctrl-F or a grep command...
It could serve as a way of essentially commenting out code, while making sure it still compiles.
I sometimes use it to force transactions / scoping:
if FALSE then find first my_record.
Why you'd pick "4 = 5" or "yes = no" instead of simply using "FALSE" is probably a matter of personal taste or a method of making it easy to find with a Ctrl-F or a grep command...
Reply by Simon L. PrinslooDoing old style reports, we often needed to raise the scope of some frames above the FOR EACH which used it, but we did not want it to become visible, as that would print headings where we did not want it.So we would typically do aIF FALSE THEN VIEW FRAME fLines.somewhere in the procedure block to raise the scope, while it would never actually become visible.Stop receiving emails on this subject.Flag this post as spam/abuse.