InfoPath Dev

I have several forms, all with the same non-repeating section for signature on all the views. In one form the Design Checker complains about the section on the newItem and the Edit views. It says "Other controls are bound to the same field or group (/dfs:myFields/dfs:dataFields/my:SharePointListItem_RW). This can lead to effects that can be evaluated only on the server." I have tried adding some empty rows above the section and creating a new section from scratch as a replacement. But as soon as the new section is created it gets the same complaint. In Advanced View the fields look the same on the bad and good forms, with the sections bound to the RW group that holds all the data fields. I see that I can right click a field, click 'More', and create a section bound to that field that does not get the complaint from Design Checker. I don't know all the effects of having my section bound to a field. My sections use 'hidden' conditionally. Is binding my sections to a group the way to go? Any idea why one form gives the complaint and not the others? Thanks

I bind sections to fields regularly and have not had any performance issues due to that that I've seen. In your forms without the warning, do you have other controls bound to the same field? I.e. - both a section and a field where the user fills out values are bound to the same field? Do the fields that you are binding your sections to have rules in both the forms with and without the warnings?

None of my sections in any of my forms are bound to fields, as far as I can tell. Rather they are bound to the group ....RW. They are the same in the good forms and the bad one. I think I was adding or changing something in the section on the bad form too fast or with an error, that is now fixed, but the error elf doesn't forget. If I create new sections to use, bound to fields, does it matter if it is a field that will be on a control inside the section? Or just a random field that will not be in the section? Would a new idle field be best?

I see - I misread your original post. I would not hesitate to bind any number of sections to the same group. I have never had an issue with that. Again, I don't know why you are getting a warning in some forms and not others.

If I select the section, right click, and choose change binding, then select one of the fields that are controlled in that section, then the error for that section goes away. BUT then the other 2 controls in that section complain that they are "unbound" . Binding my section to a field seems to interfere with the binding of controls in the section that are not the section-binding-field.

So that behavior is expected - if you rebind a section, you also will have to rebind the controls inside it.

Rebinding the section and then the controls inside it fixed all warnings. Thanks