InfoPath Dev

Hello!

I am having an issue with a repeating table which, upon submitting to SQL, is somehow confusing the newly inserted row with the last row of data and overwriting the 'new' row with some fields from the previous row. 

Some background:

My form is connected to several SQL tables, two of which are being written to in a 'nested' format.  I am using a Master/Detail control on the 'main' table to show more information about both tables.  The form is submitted using rules, initially it is just sent to SharePoint, and then it is reopened by the 'approver' and submtted to SQL (where upon the issue occurs).

It seems like Infopath is getting the update/insert statements confused somehow.  I can't even get this to occur every time, but it seems to happen more often when the form is saved, closed, and reopened a few times without being submitted.

HELP!

Hi Sloveless and welcome,

Have you refreshed the main data connection (needed if the DB schema changed)?

In the early days of InfoPath (2003-2004), many people struggled with mapping XML data to SQL. To help those people we created a cost-effective Web service called DBXL which is an accelerator helping people quickly integrate their InfoPath forms with SQL databases. It supports multiple databases, tables, and mapping arbitrarily deep structures to arbitrarily many tables. You can install a free trial of this from Qdabra's web site here: http://www.qdabra.com/en/products/DBXL.aspx. We guarantee it will save you time and money.

Because we spent so much time developing this generic Web service, we just can't answer every specific custom database mapping request. I'm sorry about that.

Regards,

Thanks for the Qdabra ad, I had tried it already, and since it cannot do updates (just inserts) it doesn't help.

My issue is almost identical to this post:

http://www.infopathdev.com/forums/t/25002.aspx

I am going to try that solution.

Thanks for trying it.

The reason it doesn't do inserts is by design. You can't have a loosely coupled SOA architecture that has a tight DB schema coupling (which is what updates require). Since we store the data in XML as primary store, the DB tables become simply a downstream output for reporting and line-of-business integration.