InfoPath Dev

I have an infopath form that is based on a SQL database. I want to have a general section that should be filled by users all the time, and another optional section that contains a repeating table. I can't figure out how to design the database and the form so that the data in the repeating table will be saved in the SQL database.

To be more clear, the general section contains information about the user and a project they are planning, the optional section has repeating table with fund source, account number, and amount of money controls. They can enter more than one fund source. And i need to store all these.

I thought of building one-to-many relationship tables in the databse and base a master/detail control on it in the form, but the options available for submitting in the infopath form then won't include "save to a database", and i don't know the reason for that.

Any help will be very much appretiated.
Thanks.

You'll need to do this in code using custom logic. It's not hard, and should only take 5-6 hours. Send me email at Patrick.Halstead at AutonomySystems.com if you'd like us to look at your solution.

You will need to either structure your main data source such that the database returns a repeating table, or write some code to push back the repeating table values.

Ok, I was able to solve the problem.It doesn't really need any coding at all.
Just for the benefit of others, here's a general description of what i did.
I build two tables in SQL, the two tables should have primary keys in order for submit to work.
I then created an infopath form based on the database. The two tables are linked as one-to-many relationship on the primary key of the main table.
I then dragged the whole group from the data source section to the form, and choosed (repeating section with controls). This will do:)
When the user fills out the form and submit the data, it will be submitted to two tables with the general information saved in one and the repeating table information saved in the other table and the field on which the tables was linked gets autopopulated.
Hopefully this is clear enough.