InfoPath Dev

Detail,
I had 7 tables 6 were all linked with the same key. They were all originally one large table. All on a local computer, No Sharepoint involved. No Web usage at this point.
When I did a data Connection , the system disabled the database submit. There was no way I knew of getting it work.
NO ONE CAME FORWARD with a successful response.

I resolved the problem by removing the 7th table from the data connection and copying most of its data into the customer record, which seems wrong. Every thing is working. But I have to duplicate the suppliers data.

Alternative experiment
I have tried to turn  the data connection around, and make the supplier table the primary table. It has one key common with the customer transaction table. But try as I might I could not get the Form to read the  customer tables.

Guess I am stuck with the solution I tried above?

Is there any code that can be applied here?

I have to add addional table soon, A table for insurance purposes.
It will be used as an alternative, in the form, to the supplier details.

IF I ADD THE CUSTOMER KEY TO ALL THE SUPPLIER TABLE RECORDS, AND TO THE INSURANCE TABLE RECORDS,
THEN I SHOULD BE ABLE TO HAVE SUBMIT WORKING? 
IS THAT WORTH A TRY?

Hi all,

I thought I had resolved the issue of 7 tables, in an Access database in my case, with 1 the supplier table and the system disables the submit function.

I build a data connection for the 6 tables as the Primary connection.

Then Add as a secondary data connection the 7th table, the supplier table, then the system seems to work. 

The 7th table resides in the same Access database as well.
For designers, it may be anywhere!!!

It takes time to learn!!!

No,  An issue has come up where, when I re BIND the fields on the form.
A warning comes up stating that the field will be bound to the first record.

And,  it ##**^^@ did.

HELP, please someone. What to do now??
How do I access an exact record on the secondary database?

I don't want to have to copy all supplier data into the customer Invoice record each time.

There must be a solution????

If a control is not in a repeating section and is bound to a field in a repeating group in the data source, you may see this message. You may also see it if you try to bind a control to secondary data source field (even if it is repeating) when the control is on the form in a section that is NOT bound to the same secondary data source.....

Thanks for the response Hilary,  I am not quite clear on what you are saying here. 
But I think you are infering to my use of a secondary data source for the supplier.

I am currently redesigning the form with the Supplier as the primary table, much to my angst.
I will have the customer as a subordinate table.
Then I am going to load all the supplier data into the customer record.  Seems no other way.

Question 1 What do you think?

I am going to add all the other tables to the data connection and make them directly subordinate to the customer table.

I have also designed a background form, if appropriate, to be automatically called,
and use that to update the supplier fields in the customer table.
Hopefully that will work.
Question 2 What are your thoughts here?

Question 3   You did mention something about making a table a primary table (or key).  What do you mean there?

Question 4   Is there a way I could look up all my posts in one screen?

Thanks for your responses so far, and for the ones for the above..

Ian

HIlary I am running arond in circles with this problem.

I have a customer table with a customer key field - cust_nbr - the primary key.

I have a supplier table with a supplier key field - suppl_nbr the primary key.

I want to make a data conection with the cust_table as the primary table, and the suppl_table as the subordinate table.

The customer table has a field called suppl_nbr and is intended to be the link to the customer.

On my FORM I have

a table with the query keys entered. For now I am only inserting cust_nbr.

I have a table after the Query button. In that table I have a repeat section bound to the cust data record name.

In this I have all the Cust fields, and again one is the Suppl_nbr, plus a couple of other supplier fields.

Back to the Data Connection, The application will not allow me to have submit enabled because of a one to many relationship!!!!

I am NOT using  SharePoint, and I am only using Access databases.

On the screen before the close screen, the enable key is greyed out. So I cannot check it to enable database submit.

I get days when things go well. And days like today when nothing wants to work?
I get days where I can change some fields in the Access db, and the forms handle the change,
Yet I get days, like today, where I add, delete or change a field, and every field on the form gets rejected, comes up with the red icon.

What do I have to do to get this applic.  to allow a submit?
Or, get something working?  
I am missing something??

Hi, Ian:

I can tell you are very frustrated.

Can you type in (or supply a screenshot of) the exact message in the final window of the main data connection window, where the checkbox to enable submit is?

To see all your posts, click on your name in the upper right of the browser window -- it will take you to your user profile.

In your database, do you have relationships defined between your tables?

You've been through the data connection wizard quite a few times by now, I'm sure -- your primary table is the first table you add. Then you can add additional child tables to it. You define relationships between the tables as you add them.

Have you walked through any of the Office Online tutorials for database bound forms? I'm wondering if that might make some of this easier for you.

You need to understand the relationship between your database and your db bound form. If you delete a column in Access, and your form had a section (for example) bound to the field related to that column, and there were other controls in the section...the section will become unbound, and the controls in the section will as well. With a database bound form, it is a really good idea to be pretty certain about the tables and columns before spending much time on your form design.

Oh, by the way, you mention no one came forward to explain why your one large table wouldn't allow you to build a form with a submit -- I know at least once I asked you what the message you had was in the final window of data connection wizard for the main data connection -- did you ever post that? It may have helped you figure out which column was causing the issue. If you only had one table, it would have most likely been a data type issue (an image data type, or something set to (max)).

Hilary,

Apologies for the delay in responding, as I have been away due to family matters. 

Your last  point first. I put a blog message up on an Access blog site,
and some people felt I had reached the max for the number of fields in a table. (250 odd).

Apologies also for stating earlier message that there was a lack of response,  I agree I did get some responses.
Maybe in my interpretation, I felt it did not make my problem any clearer to resolution.

In reply to your comment, I am only using simple field structures (text, y/n and number).
No figures , or any other special features.
I know little about Access.
With multiple tables, it may be more involved setting up the correct field / table relationships.

I only used the suppl_nbr in the cust_table as the key field association.  It was not marked as a Primary key in the supplier table.
Maybe I should use the auto increment ID field as a key field, or one of the key fields.

After getting the One to Many warning and submit function disabled,
I am unsure how the system associates the fields in the tables. Whether cust is one and suppl many, or, visa a versa.

I am going to experiment with different key fields, tomorrow, Australian EST time,  Tues pm your time.

I think I will change the suppl key field to the auto increment ID field. Or have two fields as primary keys?

Looking forward to further discussions about this matter.