InfoPath Dev

Hello All, 

I have 2 data bases. db A and db B. I need to read from dbA and write to dbB. 

I have got it reading A and writing to B. However i need to store multiple records for B which relate to one unique number in A. eg. multiple orders (db B) per client (db A)

So does anyone have any ideas how i can store multiple records?  

When i use the submit function of the Button, it fails to create a unique ID number. It just overwrites the existing record for the client. This also works the other way round. Once you enter the client number it merely pulls up the previous order, rather than letting me start afresh.

 I have linked the table A to the table B with a one-to-many relationship, however i can’t create multiple records per store number.

 Any ideas or suggestions would be greatly appreciated.

 Regards,

James.

Are these seperate databases or seperate tables?

 Witht he default Database type form in InfoPath you would want to build it from scratch around B or what you wanted to submit to.  Then you could use other tabels as secondary data connections to recieve data and then put that into your B structure and submit.

You very likely need web services.

Some of the limitations you might encounter witht he standard InfoPath database connection is that you cannot submit to unrealated tables.  Also you cannot query secondary tables, which means you have to load the entire dataset which could be a performance issue.

With web services you could dynamically query multiple tables.  You also could submit data to multiple tables.

Are you using SQL?

How many different tables do you have?

Clay thank you for the speedy response.

 I should clairfy these are tables -  which ARE related throught unique "client ID" i.e. 1234. There are two of them.

 I will as u suggest, make the 2nd table a secondary data connection however on my previous attempts nothing has come to fruition.

 I too fear this would be more appropiate for a web based service however i have been given the tedious task of exploring this route 1st.

 Will this eliminate the problem of creating a new record for an existing client ID rather than scrap the existing record?

Thanks again,

James.

OK James.

You may be able to get by without web services.

The key is making sure your tables are related right and then when you create a new database form to include the main table as well as the child table in the main data source.

Web Services are often the better way to go since they give you a lot more flexibility and have additional functionality but you may be able to get by without. 

If you wanted to see a demo of the differences you can email me directly by clicking on my name to the left.

What you are trying to do, update records is definitely doable, it is just getting the architecture and setup correct.

Clay,

Thanks again for giving me such vital advice and assistance.

Looking forward if i encounter any more problems en route im sure you will be my first port of call.

Cheers,

James.