Hi Folks,
I have a unique column contraint (Indexed, non-clustered, Not-Null, Not
PK, the column value is nvarchar type(50)) on a dataset. I am trying to
figure out how to check for the unique value before submitting update
back to database.

I want to trap the user entry if it violates the constraint, and supply
a message dialog so the user can make corrections before re-submitting
the update.

The message only needs to let the user know that the textbox entry they
have attempted to save is already in the database, and they should try
some other unique entry.

So far, I haven't figure out how to raise the error, or trap it for
processing at the application level.
However,  the table simply does not save the violating entry; nor does
it return an error, so if a user does supply an entry that is not
unique, they will not recieve any message indicating such, and it is
not apparent until they try to look-up this new, redundant entry --
which isn't in the table.

TIA

Gary

Why?  It would be better to use the front end to format the input into
a standard format, submit it to the DB and catch the error .  If you
have the same code in the DB and the front end, then you have to update
both fo them and keep them in synch.

Would you mind demonstrating what you have said?  An example would be
quite helpful!

Thanks for your time!
Gary

--CELKO-- wrote:
Show quoteHide quote

Performance issues using Parameters
Dynamic SQL Problem..
Timeout - max pool size reached
CLR and Insert
Performance problem with SQL Server 2005