Hi

I'm just upgrading a solution developed in fmp5 to fmp7 & a calculated field is really throwing me. Although fmp7 accepts it in the define database, the result I'm getting isn't as I expected.

(Payment 1 Made Field:)

Case(IsEmpty(Contract Payment 1);"";

Case(not (IsEmpty(Contract Payment 1) and Payment Received 1 ≠ "Yes"); "No";"Yes"))

The field is mean't to log a payment made by adding a "Yes" if the above conditions in this case aren't met.

The second case statement is the one I'm focusing on that doesn't seem to work. I have checked that:

Contract Payment 1 (Has an entry - hence not(isempty)

Payment Received 1 (Has a "Yes")

As I understand it, a "Yes" should be returned?

Am I getting something fundermentally wrong - this did work in my fmp5 solution.

Thanks

Your condition is:

not (

IsEmpty ( Contract Payment 1 )

and

Payment Received 1 ≠ "Yes"

)

Both statements are false.

Therefore, your condition is:

not (false and false) =

not (false) =

true

So a result of "No" is correctly returned (surprise, computers are logical...).

Why not write simply:

Case(

not IsEmpty ( Contract Payment 1 ) ;

Case ( Payment Received 1 = "Yes" ; "Yes" ; "No" )

)

You're spot on!

Those sort of calculations always spin me out

I wonder how this slipped past me in fmp5 - as it seemed to work (granted this calculated field is only 1 of a number of dependencies - but i'm sure I would have noticed!?)

Thanks

m