InfoPath Dev

 I'm glad you had a chance to try it, that makes it easier to understand. 50 isn't necessarily too large, it somewhat depends on the complexity of your schema. Basically, you'll have to add as many instances of the repeating group as you think you'll need in the default data settings for the form. Then, the resulting XML will ...

InfoPath doesn't support dynamic columns. If you will have the same number of columns, but with different data in them, you could use different expression boxes for the headings, showing and hiding the right one based on the user's filter. But if you sometimes need to see more columns than others, you'll just have to make sure you have ...

 Hi, Winnie:  - Multi-select controls are bound to a repeating field. We can't add fields to a field - only attributes. So, if you right click your repeating field in your main data source, and select add, you can add an attribute. But multi-selects are interesting in that when you make a selection, InfoPath inserts an instance ...

 Do you see how the option button control has a little warning that it can't repeat where you have it? The reason is the data structure in your form isn't correct. However, if we just add attributes to the repeating field that is bound to your multi-select, the attribute nodes aren't included when the new instance of the field is ...

Try this one - save it locally, right click and select Design to open in design mode. You'll see two instances of the repeating section on the form - the one with the heading info is set to not allow the user to insert, and hides all but the first. Then all the fields in the heading are using defaults to set to the value of the ...

 Well, on review of the user guide & the code, it appears I may have been lying to you. :) So, now you get to help me decide the best approach for this. We are trying to get qRules 8.1 out the door (email me via the forum if you want to beta test a copy for me), and this would be a great time to add this. The simplest approach would ...

Oh, so sorry, I missed that. I'll take a look later today. :)

You may have to go with custom validation instead of just setting fields to can't be blank. Add a field to your main data source called "status" - when the user clicks the Submit button, set status to submitted. Add validation rules to your fields that have the condition that the field is blank and status = submitted. Then the ...

Wow - okay, I just reproduced this. I'd not seen it before. I think your work around sounds like the right approach, since it is working for you.

 You may need to talk to someone on your company's IT team for help. I also noticed you are using the mapped path in your code - again, since you probably can't control what the drive letter is your users have mapped, you should probably use the server name, like \\server\shares\etc, as you do in the second step of the publishing ...