InfoPath Dev

If I recall the situation correctly, the correct structure was something like: Main Repeating Section -- Non-Repeating Section ---- Sub Repeating Section -- Non-Repeating Section ---- Sub Repeating Section -- Non-Repeating Section ---- Sub Repeating Section -- Non-Repeating Section ---- Sub Repeating Section I.e. each sub repeating section was ...

Good suggestion Stavi.

You'll probably want to go with DOM. Why does this matter to you? Just curious or what?

I went and did a search for xdXDocument:get-DOM to see if there were any other examples knocking about and it turns out that it works if you make the filter part ../@CCenID = xdXDocument:get-DOM()/my:purchaseOrder/my:items/my:item/my:aCostCentre like this: ../@CCenID = current()/../my:aCostCentre ... I think. Going from memory and the code is ...

a regular section should be inside the repeating section for each one of the child tables, correct?

tried that, no change.

Yes - that is correct. Only a single submittable SQL connection. You will need to use a WS if you want multiple submittable connections.

Thanks for sharing this. Yes - you must ALWAYS remove the xsi:nil attribute before providing a value to a field. If you clear the value of a field, and it is marked as cannot be blank, then you must add back the xsi:nil attribute or else the field will show an error in InfoPath.

Did you add tree.xml as a form resource? See Tools menu.

Strange. The statement in Init() looks fine. This doesn't even require full trust. I'm not sure why you are experiencing this.