>Hello every body,
>
>I have problem with primary key, when I delete record and enter new record with same value in primary field error come value already exist. If any body has a solution, please reply
I disagree with Nancy's and Walter's advice. The PK should never be reused. It should be machine generated. It's purpose is to enforce referential integrity, in which case, you don't really care what it is...so why bother reusing it. There is an article on my website that shows a method of generating this PK.
Also, adding the FOR condition to the primary key will render it useless to Rushmore optimization. You'll need to add another tag that Rushmore can use, thus adding to the overhead.
Note to Walter: I'm not getting into this again Walter ... you always posted your opposing view point, so I'm posting mine. :)
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer