https://www.infopathdev.com:443/blogs/greg/archive/2004/07/03/Faulty-Condition-Expressions.aspx2004-07-03 I uncovered this bug today while trying to figure out why an InfoPathDev example form I&#39;ve been preparing hasn&#39;t been working correctly. I&#39;ve reported it to my Microsoft contacts, but it is unlikely that there will be any fix forenCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/blogs/greg/archive/2004/07/03/Faulty-Condition-Expressions.aspx#53810Sat, 17 Apr 2010 19:55:27 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:53810mphilipp17<p>Thanks for the post, I was having this exact problem and your post save me a bunch of time trying to figure out what was going on. &nbsp;I looked at the expression that Infopath came up with and thought to myself that the string-compare function looked funny for doing number comparisons. &nbsp;</p> <img src="https://www.infopathdev.com:443/aggbug.aspx?PostID=53810" width="1" height="1">