No, this is not true.
IF( 3 > 0, "yes", "no" )
will evaluate just fine.
IF ( 3 > 0, "yes", "no" )
will result in an error.
I have never before worked with a single programming language that would get hung up on that extra space there!
However, this is where things gets really strange.
Because Airtable got hung up on that extra space up above, you would think that it would get hung up on an extra carriage return — but it doesn’t.
For example, this function evaluates just fine:
(3 > 0, "yes", "no" )
But sure enough, if you add an extra space on that 2nd line like this, then it produces an error message:
_(3 > 0, "yes", "no" )
(The underscore above represents the extra space, because this discussion board won’t let me add a space at the beginning of a line.)
But — the good news here is that I’m starting to figure out that there IS some consistency to where Airtable refuses to allow spaces — and it seems to be near the beginning part of each function.
I’ve been programming in FileMaker Pro for 30+ years, and all spaces are irrelevant… so I’ve never encountered anything like this before. In FileMaker, all 4 of the above scenarios are evaluated completely 100% identically.
I almost gave up on Airtable in my early days, because I couldn’t get any of the formulas to work! Lol.
Interestingly enough, FileMaker also understands that ≥ and >= are the same thing, so @Pamela_Giles would never have had her problem to begin with!
I totally love Airtable as a lightweight relational database system, but I do feel like the Airtable folks could do a “little more polishing up” on their end to account for these minor differences in typing formulas.