>Maybe you shouildn't allow the error to happen in the first place?
>
It is an error exactly. I can't prevent a user from entering a duplicate value in an ID field. The only way (as far as I know) to trap it is when UPDATE SQL is sent to SQL Server to see what is returned. So I need to inform the user that this entry has been already assigned to another record/row. If you know of a better way to do it, instead of using SQL Server to return an error, please let me know.
UPDATE: I meant to say, "it is NOT an error exactly"
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
