Hi Ludwig - is your issue surrounding the management of data entered by repeating sections onto your sharepoint list or the use of data once it is in there?

We have found that when you hook-up the data-set from infopath to a list for repeating values the list will handle this by simply adding to the text field on the same row. So if one incident ref has three repeating entries as "example1" then "example2", then "example3" it will appear as "example1,example2,example3"

I am not sure what you mean by external data types, but in terms of making the list accessible to other databases the easiest way is to link the sharepoint list to an access database via the actions taks bar at the top of the list. This makes the list appear as an access database table - and although it is not dynamic (list changes need a refresh on the database to come through), it has potential. Obviously this is most straight-forward example but we have found that SharePoint lists are accessible to most Microsoft systems (possibly sql server as well?). so making this data available to other platforms is possible.

Regards, Rob

Hi Rob

Thx for the reaction. Yes, we solved the problem to store "header-field"relationships in a infopath form in a relational database, e.q. in our case SQL server via the use of smart objects..

Regs

Ludwig