https://www.infopathdev.com:443/forums/142.aspxAre you exploring new features coming up in 2010? Share information and ask questions here!enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/101186.aspxThu, 12 Feb 2015 22:29:22 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:101186Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/101186.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=142&PostID=101186<p>Yuck, what a pain. Honestly, this is one of those cases I&#39;d save the form as source files, open manifest.xsf with a text editor and search for the field that is getting set. The ruleset will have an identifier - usually you can search for that and find the field w/ the rule - but if it is on a button it can be trickier (if your buttons are named Control1234, etc. )</p>https://www.infopathdev.com:443/forums/thread/101177.aspxThu, 12 Feb 2015 21:13:36 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:101177dapklp0https://www.infopathdev.com:443/forums/thread/101177.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=142&PostID=101177I&#39;ve seen this question asked, but not really answered. Because there is a &quot;processing error&quot; in running Rule Inspector, I get no results for &quot;Rules that may change this field or group.&quot; The bottom line is that I need to locate a rule that is changing a field undesireably and have no where to start looking, except for hide-and-seek.