InfoPath Dev

I have recently completed form, that I have just found out needs to also be submited to a database.  I read that to do this natively in InfoPath, I have to select it prior to building the form.  That being said, would it be easier/better to recreate this from, or use a sharepoint workflow to trigger when the form also gets submited to a sharepoint form library (wss 3.0) which it currently does?  I'm assuming it will be easier to rebuild the form, though no easy task, so I have a few questions about the sql route.  

1.  Should I have one database per form, OR, one InfoPath database, with a table for each form?  Any best practice for that?

2.  Question 2, I have an optional repeating section for name on my form.  How will sql handle that?  Can it?  Will it create a 2nd record with all the same info and just a different name?  (that would be ideal).  

Warning, I'll probably have 100 more questiosn to whoever responds to this. :-)

Best Practice is to get webservices, like the tools from www.qdabra.com, and then you can take your existing form and have it submitting to your DB in under an hour.

As far as Table setup.  You typically want to look at your main schema and any repeatin nodes in your schema would be relational child tables in the DB.  Each form would be a record or set of records.

The optional is tough, that would need to be a related table and would exist for each optional record.

I'm liking the under an hour with qdabra.  I see there is a trial version.  could i set this up with the trial version do you know or would I have to buy it to do this.  Also, are there any tutorials or good reads for doing something like this with qdabra?

Hey, Eric:

Installation instructions for DBXL can be found here. I'd suggest reading the server scenarios first to decide where best to install the trial version in your environment. The beta for v2.2 is here.

You get so much more flexibility with DBXL. I have a couple of blog posts on mapping, Ernesto has posted a bunch of documentation in the downloads, and, of course, you have my email if you get stuck.