I use <= and >= because I can type it without clicking (and it's more universal).
also, <> for not equals.
Or you can type up the calculation in the calculation editor--you can use a watch expression in the data viewer if you have advanced and then you should be able to paste your expression without substituting characters. (Though like David, I'm reverting to >= etc more and more given the recent updates in the scripts workspace...)
Great thanks. I've tried them out but wanted check for strange exceptions.
Just to clarify: Does it matter which way around "=" and "><" are? Eg. => or >=? And Phil were you cautioning that it might be generally better to use this type of syntax rather than > or <.
1 other syntax query for the same purpose. I've been using a 'Case' function to check whether the 'v6_n' field blank and check for the v1_n field being >5, but the following doesn't appear to work in the Case function equation:
T::v6_n = “” and T::Eq1_a >4. How do I check for a field being empty (if T::V6_n had an entry it would be a simple check for T::Eq1_a >5 without checking T::v6_n).
Does IsEmpty ( ) not work? That's the obvious calc it seems to me.
your condition should work as is, or with IsEmpty. Sometimes, IsEmpty "fails" because the field appears to be empty, but actually contains spaces. If that's possible, you might try IsEmpty(Trim(textValue)) ...
IsEmpty(Trim(T::v6_n)) and T::eq1_a > 4; result1;
I think there must have been a syntax error in my calc as the "" approach worked.
Back to a previous Q, does it matter if you use the order =< or <=?
And re. Philmodjunk's comment "I'm reverting to >= etc more and more given the recent updates in the scripts workspace", I don't have FM 15 (got 14) what's the advantage of these 2 characters over > or <?
'=<' and '=>" is invalid syntax (though the latter looks nicer than its valid counterpart '>=' …).
btw, at least on the Mac, the characters ≤, ≥ and ≠ are just an alt-key-press away – but with <=, >= and <> you don't have to mentally switch gears when writing SQL queries.
Good info, thank you.