https://www.infopathdev.com:443/forums/41.aspxIf you're not sure where to ask your question, ask it here. If necessary, our moderators will make sure it gets classified in the correct board.enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/18410.aspxTue, 24 Oct 2006 08:42:10 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18410Agni Jonnalagadda0https://www.infopathdev.com:443/forums/thread/18410.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18410These are the same cases I expect. <br />I wasnt talking about giving boolean values in the field.<br />I was more talking about a way we can achieve boolean results from not() also using not(field1 = "true").<br /><br />Thanks for the discussion here.https://www.infopathdev.com:443/forums/thread/18409.aspxTue, 24 Oct 2006 06:14:33 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18409hotikisu0https://www.infopathdev.com:443/forums/thread/18409.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18409Thank you Agni Jonnalagadda.<br /><br />I understand that a result of a Boolean operation was reflected by an not() expression, example "field1 = field2".<br /><br />I think, we expect of not(string(field1)) function result "true" when fied value is "false", and expect "false" when field value is "true". But not(string(field1)) result "true" when only field1 value is blank.<br /><br />----------------------------------<br />field1 value / not(string(field1))<br />----------------------------------<br /> true / false<br /> false / false<br /> blank / true<br />----------------------------------<br /><br />If these are different as a result of you, it may be a bug of a Japanese version if it lends it. Or I may neglect the check that I must do something of.https://www.infopathdev.com:443/forums/thread/18408.aspxMon, 23 Oct 2006 19:01:56 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18408Agni Jonnalagadda0https://www.infopathdev.com:443/forums/thread/18408.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18408Hmm, all of this depends how you use not function<br />if you use it on a node then it works the way you have given. If a "not" is applied on a condition like "field1 = field2" then it will negate the result of "field1 = field2".<br /><br />If you use some other functions in then it works the same way as above. for ex:<br />not(string(field1)), will give you "true" when field1 does not have any value in it and "false" when field1 has any value in it.https://www.infopathdev.com:443/forums/thread/18335.aspxThu, 19 Oct 2006 11:46:02 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18335hotikisu0https://www.infopathdev.com:443/forums/thread/18335.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18335A not() function does not do movement to expect. Even if a not() function appoints a field in an argument, I do not turn over the Bour negation of the field. A value of a not() function is always "false".<br /><br />Seemingly this looks like a bug, but it is different. The reason is so. An argument of a not() function watches existence of a nodeset.<br /><br />If you want to check behavior of a not() function, please please test next.<br /><br />(1)Make a new form.<br />(2)Create table including a field, name of "field1".<br />(3)Create experiment box, set a function "not(field1)".<br />(4)Preview the form.<br />(5)Check a experiment box is "false".Because field1 nodeset is exist.<br />(6)Delete a field1.<br />(7)Check a experiment box is "true".Because field1 nodeset is not exist.