InfoPath Dev

              this.Errors.Add(errorNode, "USER_DEF1", "the error message", "the more detailed error message", 101, ErrorMode.Modeless);

The error is added succesfully to the FormError collection. When I try to submit the form, shouldnt I see that the textbox (which is bound to the errorNode) with a red dashed line and not be able to submit the form ? It seems that this error is ignored, I can even submit the form.

For another node (bound to another text box) the same line of code works perfectly and I get the red dashed line.

Does anybody have an idea what might cause this issue ? 

Thanks, Alin 

How strange! Especially since the code is working for you on a different node. Is there anything else that might be affecting the value of that field and possibly causing it to re-validate and succeed?

The only thing which is different is, that this node is bound to a text field in one view, and to a drop down list in another view. Might this be an issue ? (The other node, where the code is working, is only bound to a text field in one view).
But I have the same form available in Infopath 2003. There it works, the issue only showed up after migrating to 2007.

I have seen a similar issue when migrating forms to Infopath 2007. In one case, there was also an error that was "invisible". I changed the text box to a label, then I saw the read dashed line. I changed it back to a text box and I got the red dashed line also for the text box. Strange... !

Stranger still! How about the Design Checker? Any clues there? What happens if you temporarily place another control on the form that is bound to the same node (the one where the error isn't showing on the current controls)?