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/18127.aspxThu, 30 Mar 2006 13:09:43 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18127Matt Faus0https://www.infopathdev.com:443/forums/thread/18127.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18127I just tried this with SP2 and could not reproduce, maybe it was one of the fixes?<br /><br />Anyway, good eye and thanks for the info!https://www.infopathdev.com:443/forums/thread/18006.aspxThu, 30 Mar 2006 09:43:54 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:18006pcapsey0https://www.infopathdev.com:443/forums/thread/18006.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=41&PostID=18006Hi folks,<br /><br />I came across this by accident, trying to replicate all of the things that users might do...<br /><br />To recreate the bug:<br />1 - Create new form with 2 text field controls and a button control.<br />2 - Set Conditional Formatting on the button so that it is disabled when the first text field is blank.<br />3 - Preview form. Enter text in first text field, and click the button without tabbing out of the first text field. The button should still be disabled.<br />4 - InfoPath crashes.<br /><br />We're running InfoPath SP1 on Windows 2000 SP4.<br /><br />Regards,<br /><br />Pete