Well I guess the best way to answer your question would be to write the code to catch any sql exception and print out the error. So basically, create the violation on purpose and see what you get. I have had to do this in the past to see what kinds of errors SQL Server would throw back to .NET
Look at the table you're tring to insert into, specifically any unique keys (primary and alternate) it might have on it. What the error is telling you is that you're tring to insert a second row that has the exact same key as a row that's already in the database.
Chip H.
____________________________________________________________________
Donate to Katrina relief:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.