Is this in a calculation field or in a text field with an auto-entered calculation? It might not update to show this message if it's an auto-entered calculation.
Are you sure the field is truly empty and does not actually contain text that is not visible? A space, a return and a number of other non-printing characters might be present in a text field--causing it to look empty when it is not actually empty. Double click the field and see if anything Highights.
PHP has a function called empty(). FileMaker has a function called isEmpty().
If the problem isn't simply a typo, get FileMaker to give you some information, you can use Length( Field1 ) and code(Field1) to discover what you have.
I think this is a calculation field (the field type is "Calculation", not "Text") however, the calculation result is set to "Text".
I just double checked Field1 to make sure it was "" and not " ", and was able to confirm there are not spaces between the quotation marks.
How weird is this? Could it be a relationship issue?
once again, I'm piggy-backing on Phil's post ... If there are "invisible" spaces in your data, use this:
if ( Isempty ( Trim(Field1) ); "Missing Information"; "" )
I just tried your suggestion but no such luck. Field2 remain empty along with Field1. Could it be because Field1 is located in a portal? I don't know why that would affect this calculation but nothing else makes sense.
Helpless in Texas.
So I had to ask my very busy boss and he helped me figure it out. It was a relationship issue. First, I had to change Field1 to a different field (I was already using for something else) that uses the List function (a calculation field), which also happened to be in a different table than my original Field1. Next, I had to relocate Field2 to that same table table, then use the If(IsEmpty(Field1),"Missing Information";"". So the two things I erred in were:
1) the relationship / location of the fields, and
2) I should have used the list function to calculate for Field1.
I hope this makes sense and helps anyone else who may encounter the same problem. Thank you so much Phil, Malcolm, and David for your help!