https://www.infopathdev.com:443/forums/190.aspxView and edit existing forms without InfoPath - includes most qRules functionality!enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/125624.aspxMon, 03 Feb 2025 19:32:46 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125624Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/125624.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125624Well done! :)https://www.infopathdev.com:443/forums/thread/125623.aspxMon, 03 Feb 2025 19:29:35 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125623sbhunter0https://www.infopathdev.com:443/forums/thread/125623.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125623Never mind :) The field/control bindings hadn't been properly set. I did so via Infopath Designer; didn't see a way to do so from the FV designer. I'm guessing that, since the controls weren't bound to anything, any chance the webform got it reset them. Anyway, thanks for letting me work it out on my own!https://www.infopathdev.com:443/forums/thread/125622.aspxMon, 03 Feb 2025 16:47:22 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:125622sbhunter0https://www.infopathdev.com:443/forums/thread/125622.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=190&PostID=125622I have a form with 4 sections arranged in the following manner: a string-backed checkbox is used to determine if a section of other string-backed checkboxes gets displayed or not; specifically, the section is only displayed if the "mater" checkbox is checked. This show/hide functionality works as expected. One of the 4 sections also works otherwise as expected. But with the other 3, toggling any of the "master" checkboxes unchecks all "slave" checkboxes, even in sections not associated with that master. This happens even if I remove the conditional hiding of these sections. These "erasures" happen even when I toggle other checkboxes at the same level as the "masters" (think of them as masters w/o any slaves). Note that the slaves subject to this problem also are not saving their values to the submitted record, which seems too coincidental to not be relevant, but I have no idea how. The slaves in the section that doesn't show this problematic behavior also get properly saved. Any ideas as to what might cause this (these?) issues, or where I might look for the cause of the problem (if not the solution)?