How do I eliminate Error 3002?

Very late to your question, I had the same issue and discovered that the entity framework designer had identified my "ScoreId" column (relative to your PersonModelScore table) as a primary key column. I changed my setting to false for my ScoreId, and all worked well afterward.

This fix worked for me. One table had two primary keys when it should have only had one. – Jesslyn May 19 at 21:14.

You should create a single Identity key for each table. ModelScore should have a ModelScoreId, PersonModelScore should have a PersonModelScoreId. References between table should be a single field.

Thank you for your suggestions. Now, how does this solution still preserve the integrity of the data model? Each Person is associated with no more than one of each Model, and the ModelScore must be a valid ModelScore for that Model.So, I think PersonModelScore would either have to have both a ModelId and a ModelScoreId, which is redundant and requires verification, or just have ModelScoreId, which requires verification that there are not multiple ModelScores per Model per Person.

Neither way seems to work very well, in my opinion. Is this just a limitation of Entity Framework, then? – Andrew May 20 '10 at 19:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.