InfoPath Dev

Ok.....so I guess my advice would apply to the other section that requires the the checkboxes.

Why not just use a rule to set the second checkbox to the same value as the first checkbox.  No need for conditions or multiple rules.

Yes, it should work fine.  Look at the properties of the checkbox you want to automatically check, and make sure that the checked value is true.

Yes, the descriptions are coming from the my:Activities group, which, along with my:Code, I set up using InfoPath's Default Values dialog. The logic in the form comes from: All three repeating fields being bound to the same my:Activies group Section controls inside the third repeating section, all also bound to the my:Activities ...

Here's a form that does what you describe.  But the way your categories have people's names in them suggests that these categories might be modified quite often.  Is that the case?  If so, I think a more general approach may be in order.

Would the second table in the attached form do the trick?

I'm not sure what you're asking.  The sections should automatically be ordered based on the order of their respective start times.  Are you asking me to explain the mechanism that I used to order the sections based on their sort order, or do you want a way to change the sort order to something other than the order of the start ...

Might this be more like it?  The sort order number is automatically determined using the default value formula on the Sort Order field, based on the times and whether the Include checkbox is checked.  If that's still not what you're going for, might you attach a mockup of what you want this final view to look like?

Another approach is to use an outer repeating group with the nodes in it generalized to be able to represent the data in any type of section, like in the attached form.  One benefit of this approach is that you can have more than one of the same type of section (which you may want).  Under this design, you could use the Up and Down ...

It's a bit rough, but I think the attached form might do what you're looking for.  The key points are: An editable repeating node (my:Activity) to describe the order of the sections. Another non-editable repeating section bound to the same node. Individual non-repeating sections bound to the same node, with conditional ...