IF statement is broken in Numbers version 10.0 (6748)

New Numbers version 10.0 (6748).


Cell A1 Enter a number (eg 5)

Cell B1 IF(A1=5; "It's five" ; "Not 5")


Returns a "red triangle of death".


A perfectly functional spreadsheet I've been using for years was covered in these red triangles when opened in the new version when I (mistakenly) "upgraded".


It took me ages to work out that a core problem was one of the oldest and most basic of functions in the Land of Spreadsheets. The IF statement. And what *else* is faulty?


Before I convert everything to Excel (an appalling product but at least its FUNCTIONS work) does anyone have any ideas?



MacBook Air 13", macOS 10.14

Posted on May 5, 2020 4:53 PM

Reply
Question marked as Top-ranking reply

Posted on May 5, 2020 6:21 PM

So Numbers now requires a comma delimiter (no more semi-colon) and FileMaker requires a semicolon (it automatically converts commas).


Good one. It seems the concept of basic standards of syntax has gone. I'd prefer a coding error actually as that could be fixed. But cultural problems are even worse. But of course... Numbers people and FileMaker people wouldn't even know where the others are located let alone *talk* to them. And I find it hard to remember that Apple is a phone company and computers are a legacy thing. 2020 is full of disappointments, eh?


OK. So I've got a big editing job to do.


Not your doing. Truly thanks for your help Wayne.

4 replies
Question marked as Top-ranking reply

May 5, 2020 6:21 PM in response to Wayne Contello

So Numbers now requires a comma delimiter (no more semi-colon) and FileMaker requires a semicolon (it automatically converts commas).


Good one. It seems the concept of basic standards of syntax has gone. I'd prefer a coding error actually as that could be fixed. But cultural problems are even worse. But of course... Numbers people and FileMaker people wouldn't even know where the others are located let alone *talk* to them. And I find it hard to remember that Apple is a phone company and computers are a legacy thing. 2020 is full of disappointments, eh?


OK. So I've got a big editing job to do.


Not your doing. Truly thanks for your help Wayne.

May 5, 2020 6:15 PM in response to Slartibartfast_Rules

Well, my first idea would be 'Maybe we should read the error message."


My second would be similar to Wayne's "Have I accidentally changed the language and region setting to a region that uses the full stop ( . ) as the decimal separator?" If you usually use semi colons ( ; ) as the separator in formulas, your region should be set to one that uses a comma as the decimal separator.


So what was 'faulty' about the IF statement? And what did you do to fix it?


Beyond that, there are several ideas, but they'd all be guesswork, as you haven't provided much information on which to base a 'reasoned' idea.


Regards,

Barry

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

IF statement is broken in Numbers version 10.0 (6748)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.