I am getting this particular error....

Violation of PRIMARY KEY constraint 'PK_tblTempOnlineFWApplicant'. Cannot insert duplicate key in object 'tblTempOnlineFWApplicant'. Violation of PRIMARY KEY constraint 'PK_tblTempOnlineFWCompany'. Cannot insert duplicate key in object 'tblTempOnlineFWCompany'. Violation of PRIMARY KEY constraint 'PK_tblTempOnlineFWPaymentReceipt'. Cannot insert duplicate key in object 'tblTempOnlineFWPaymentReceipt'. The statement has been terminated. The statement has been terminated. The statement has been terminated.


But what is actually confusing me is that when I check the database the information is actually in it. I don't know why it's throwing up this particular error. Help

Is your database set up with referential integrity? How is your sql inserting these records?

Kevin

dartcoach

That's a pretty terse question... What action are you taking that raises these errors? Are you sending the SQL directly, using one of the super gizmos .NET gives us, or what?

What is the actual action with respect to the DB?

You say the data are there. All of them? I mean, something failed...

What operation are you doing on the table tblTempOnlineFWCompany - Insert or Update.

The error would come when you insert a duplicate record to the table, that is, the table already has a record by the primary key you are inserting.

In that case, you would have the Primary Constraint violation error. A good technique would be to check the presence of your record by primary key and then insert the record if the record is not availab;e. If the record is already available in the table, you can update the record instead of insert

Cheers
Shasur




http://www.dotnetdud.blogspot.com

I vote for the idea that your code is calling the database insert twice. That is the only explanation I see that could supports the legitimate presense of data but also the presense of an error reflecting a data insert problem which would result in no data.

What event are you handling that fires off the insert? Is it possible that this handler or the method that is actually doing the insert is being called twice?

-Peter

thanks for your replies. I found what was wrong:D

And it was?

In the code in was running the procedure to enter a record id twice.