InfoPath Dev

I have a SharePoint site with custom dataviews, links and all sorts of stuff all centered around my main "Incident Report" infopath form. This form is created from SharePoint via a form library and filled out then submitted back to SharePoint where all the magic begins with workflows on-new that set fields on the very form, create list items etc. This from walks through a handfull of statuses each that trigger workflows on the site and so on.

 I'm looking to have the form also submit itself to a SQL database for more detailed reporting. This means to me that I need to take the form and map it to submit to DBXL, then from DBXL create the SQL maps. My questions are as follows.

 1. Should I remove each of my current "submit" buttons that first save and name the form upon first submit. Also should i remove my "Save & Update" submit buttons currently that use a separate dataconnection which does not over-write allowing the form to be opened edited and saved? If I remove my submit buttons should I leave all the submit functions to DBXL to submit back to SharePoint for me?

2. Should I leave all my submit/update buttons along and simply add a dataconnection to DBXL which would reposit the form there and have DBXL then submit it for me to SQL? This meaning that my submit to SharePoint will be done directly via the form whilst my submit to DBXL then to SQL would be one via WebService to DBXL then DBXL would push to SQL?

3. Whichever version you kindly recommend I have the last question please. Mechanically speaking, I have a DFS Share where I save my infopath templates. I save them anytime I edit them then publish them to SharePoint now updated. In the case where I'm using DBXL also, is my process to save my form after editing it to my DFS share, then copy that form template to the DBXL Admin tool and publish the same template from my DFS Share?

Or do I save my edit to my Share, publish to SharePoint, then grab the actual template file from the Form Library in SharePoint to put that one inside my DBXL admin tool?

4. This last point is more so an issue then advice. In testing I found that my "On-New" workflows that work when I submit a form to sharepoint directly work as normal but seem to have issues and sometimes fail when the path is "Form submitted via webservice to DBXL, then DBXL puts the form to SharePoint". It's as if the form is locked and or not released ontime before the workflows want to start doing things like setting a field?

Sorry about the huge post, I just want to be really clear to save time.

In order to send the data to SQL tables you'll need to submit the form to the DBXL web service. From that stored XML, DBXL can send data to SharePoint form libraries and to SQL tables.

If you have a submit operation to DBXL and a submit operation to SharePoint, your xmls can get out of sync. If this happens, then your Excel report (based on the data DBXL sends to SQL) will show different data than SharePoint. I haven't even tried this but it just seems like a recipe for disaster.

SharePoint workflows at times present issues when working with DBXL, because DBXL needs to "own" the xml and push out the data to SharePoint and SQL. You'll see that illustrated here. It sounds like you already encountered an issue integrating the pre-existing SharePoint workflow into a new DBXL solution.