error at save in to 2 tables they have relationship one-to-many

hi all

I have 2 tables Customers and Orders it have relationship one-to-many and i set the cascade between tables. i add both tables to one form and i set EndEdit event to the CustomerBindingSource owing to Saves the new record in Customers before save new record to the Orders but i receives error :
A foreign key value cannot be inserted because a corresponding primary key value does not exist.
I did no know what is wrong !




Attachment 94145

That means that your child inserts are being done before your parent inserts. Please the relevant code and ONLY the relevant directly in the thread. Don't make us jump through hoops unnecessarily. If the code is in your post then we can see it without navigating to nay external sites or downloading anything. Take the easy option first and only go the harder route if necessary.

the code in save button :

Code:

---

  Private Sub CustomerBindingNavigatorSaveItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CustomerBindingNavigatorSaveItem.Click
        Me.Validate()
        Me.CustomerBindingSource.EndEdit()
        Me.OrdersBindingSource.EndEdit()
        Me.TableAdapterManager.UpdateAll(Me.Database1DataSet)

    End Sub

---

in the load form:

Code:

---

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Me.CustomerTableAdapter.Fill(Me.Database1DataSet.Customer)
        Me.OrdersTableAdapter.Fill(Me.Database1DataSet.Orders)
    End Sub

---

and one line at add new row in :

Code:

---

Private Sub OrdersBindingSource_AddingNew(ByVal sender As Object, ByVal e As System.ComponentModel.AddingNewEventArgs) Handles OrdersBindingSource.AddingNew
        Me.CustomerBindingSource.EndEdit()
    End Sub

---

and the last thing i set the cascade between Datatables in DataSet.

In theory, UpdateAll should handle related data. It appears that it's not in your case. Try calling Update on the table adapters explicitly in the appropriate order and see if the issue goes away.

Quote:

---

Originally Posted by jmcilhinney

Try calling Update on the table adapters explicitly in the appropriate order

---

Sorry, but I am weak in the English language, I hope to explain to me what you mean
thank you

Call Update on your parent table adapter first and then call Update on your child table adapter.

Yes Mr.jmcilhinney I do it :

Code:

---

  Private Sub CustomerBindingNavigatorSaveItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CustomerBindingNavigatorSaveItem.Click
        Me.Validate()
        Me.CustomerBindingSource.EndEdit()
        Me.CustmerTableAdapter.Update(Me.Database1DataSet.Customer)
        Me.OrdersBindingSource.EndEdit()
        Me.OrdersTableAdapter.Update(me.Database1DataSet.Orders)

    End Sub

---

But The-error still appear ! Is there any mistake in the code?

Is there any suggestion

you need to create a DataRelationship between your two tables... right now, as far as VB is concerned, they are just two tables in the dataset... it doesn't know that the ID of one is the FKey of the other... there's no parent/child relationship in the dataset.

-tg

Mr.techgnome did that in the photo is not DataRelationship ?

http://img822.imageshack.us/img822/1672/errorsave1.png
http://img706.imageshack.us/img706/5059/errorsave2.png

plz explained to me what you mean to do it.

thanks

What is IDCustomer? Datatype and definition... is it an Identity (or AutoNumber?) How does it get set? What is its source?

-tg

OK, I think I see the issue now. In the DataSet designer (your first screen shot) try editing the properties of the DataRelation (the line joining the two DataTables) and set the action on Update to Cascade. I think what's happening is that your app is generating temporary IDs for records in both DataTables but they are not the same as the final IDs generated by the database. Your child records contain the temporary IDs from the parent table so, when you try to save them, no matching parent ID is found. When you save the parent records, the parent DataTable should be refreshed with the final IDs generated by the database. By cascading updates, those values will be pushed to the child records also, so the IDs match when the child records are saved.

Mr.techgnome

IDCustomer
Data type: int
Identity: true
allow nulls: no
Unique: yes
Primary key: yes

I notice that you say in your first post:

Quote:

---

i set the cascade between tables

---

Did you do that in the database or the application, because post #10 indicates not in the database. If Updates are already cascading across the DataRelation then maybe the parent table is not being updated. Try saving just the parent records and see if the IDs in your DataTable match those in the database.

Mr.jmcilhinney I Chang the Update Rule to cascade in the Database and test the app put still error appear.

see :

http://i46.tinypic.com/23j0tis.png

Quote:

---

Originally Posted by jmcilhinney

Try saving just the parent records and see if the IDs in your DataTable match those in the database.

---

I try to save the parent only and it is save then close the form and reopen it and try save child and it is saved ok put that is not what i need any way i make search then I find solve but it is complex code must write it in the TableAdapter class http://blogs.msdn.com/b/bethmassi/ar...-database.aspx
is there any Idea easier ?

Quote:

---

Originally Posted by ebrahim

Mr.jmcilhinney I Chang the Update Rule to cascade in the Database and test the app put still error appear.

---

It's no use just changing it in the database because that's not where it's needed. It's needed in your DataSet so did you regenerate the Data Source after making that change in the database?

Quote:

---

Originally Posted by ebrahim

I try to save the parent only and it is save then close the form and reopen it and try save child and it is saved ok put that is not what i need any way

---

Maybe if you actually did what I said then you might get a useful result.

Quote:

---

Originally Posted by jmcilhinney

It's no use just changing it in the database because that's not where it's needed. It's needed in your DataSet so did you regenerate the Data Source after making that change in the database?Maybe if you actually did what I said then you might get a useful result.

---

Yes i regenerate the data source but still the error , but may i ask u To look in this link
http://blogs.msdn.com/b/bethmassi/ar...-database.aspx
I think that the problem needs Trick

Sorry error add