InfoPath Dev

Please ignore previous post. It is solved. Because of language issues (I work in a Dutch version of InfoPath) I couldn't get the test for A = "true" working. No matter what translation and spelling of "true" I used, it never worked. I first 'solved'' this by using the true() (in Dutch: Waar()) function. I now ...

A new mystery popped up... I'm still getting some strange behavior after removing the rules that interfered previously. My formula: A = "true" and B = "true" and (x != "" or y != "" or z != ""). I assume that as long A and B are true, only one of the fields x,y or z has to be not empty for the ...

My first reaction to that suggestion was: of course not... if there is a rule I'd know about it.... but sure enough something that I had tested/tried weeks ago was still there and interfered with my 'empty test'. So problem solved :-) Thank you Hillary

PS Sorry about the absence of line breaks in my message. Google chrome somehow removes them

Thank you Hilary. Other projects came up so it took me some time to react. I created a simple example tot demonstrate the issue, but I couldn't replicate the problem. In this simple example it just works as expected. It looks like this might be a bug because in my original 'real' form, the exact same check for emptiness doesn't ...

After I entered the data I did indeed need to click in another field to trigger the calculation to change to 'not empty'. After completely clearing the field I again clicked in another field, which must have triggered the calculation in the same way as it did before. However / where ever I click, the status remains 'not empty'. ...

I'm clicking out of the field. I can see how that could potentially have a different effect, but unfortunately there is no way to tell what the user might do, or is there? Thank you

 In my form if a specific field is left empty, some action needs to be taken by another user. I use a simple test like so:  FieldA != "" as suggested in this thread http://www.infopathdev.com/forums/p/28619/98451.aspx . Sure enough if I enter data into it, FieldA is no longer considered empty. However, if I then delete this ...

 ah! I get it. I had to take it much more literally than I did. The  A ! = "" or B != "" or C !="" is actually entered and results in a true or false (without IF-Then etc), which is in turn the actual value. I would have thought this required the Result field to be a Boolean but apparently it works as well ...

Thank you. I'm not sure I quite get it, though. How can A ! = "" or B != "" or C !="" be a value? This to me is a condition and not a value, and even then, what would be the syntax if I actually wanted to enter such a condition/value? If you could clarify this, that would be great. Thanks for your time.