using a compound if function

[Lougee]

I'm using John Osborne's visibility trick to hide a menu button when it's not applicable. I defined the field 'visibilityLodging' as a compound IF function -- if (attending? = "yes" and commute? = "stay", 1,""). The relationship is valid (visibilityLodging on the left; constant on the right) and the correct fields are in the correct portals.

Can anybody tell me what I'm doing wrong? Does the visibility trick not work on a compound IF? Or (horrors!! ) have I defined my field wrong? It seems such a simple thing and I don't get any FM error message when I save my field definition.

Feeling totally brain dead -- ti's been a long, hard day...

I know that someone out there (probably EVERYONE out there) can give me the right answer.

Abbe

[Vaughan]

For testing, first make the calculation really simple -- like =1. Then see whether the protal is doing its thing correctly. If its not then fix it. If it is, then the calc needs looking at.

[MeltDown]

Do your field names actually contain "?"....sometimes fields with such characters don't do well in calculations. Just a thought!

[jasonwood]

Do your field names actually contain "?"....sometimes fields with such characters don't do well in calculations.

This was my initial thought, but I checked and it seems that ? is not on the list of forbidden characters.

I think what you have to do is break it down first and try one at a time before you combine them. You might find that there is a problem somewhere else.

[TSilvan]

Your compound IF statement is fine, and there is no problem using such a statement as the driver for portal invisability.

Just a wild guess, but you might like to check whether the visibilityLodging and constant fields that are used for the relationship are both the same result/data type. If, for example, one of then is set to produce numbers and the other is set as text, then that could lead to a problem!! ...

[jfmcel]

Maybe the calculated key is an unstored calc. That will disrupt the relationship. If it is unstored, try to change it to indexed.

I see now that your calc is on the left side of your relationship, so this is unlikely to be the culprit.