Traping SQL returning errors

Question

Post reply

Traping SQL returning errors

damos

Grasshopper

Points: 11
More actions
December 16, 2003 at 12:51 am

#101809

How can i prevent a ADO application (Client side) to not recieve errors from SQL sever
for example i use a procedure for inserting but the user dont care for duplicate values
SQL server return a uniqe violation for the Index Its easy to do it on the client side but on the server side i always haves the message ????

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

David Burrows SSC Guru Points: 65143 More actions · Answer 1

Check if the key exists before inserting.

Far away is close at hand in the images of elsewhere.
Anon.

noeld SSC Guru Points: 96590 More actions · Answer 2

in other words :

INSERT INTO TABLE(x1,,...) VALUES (@x1,@x2,...)

WHERE TABLE.PRIMARY_KEY <> @YOUR_PRIMARY_KEY

Edited by - noeld on 12/16/2003 06:57:22 AM

* Noel

cneuhold Hall of Fame Points: 3375 More actions · Answer 3

try using an *exception handler* on client side ...

best regards,

chris.

tbonty Newbie Points: 3 More actions · Answer 4

You can try to do something like this:

If exists(select * from table where key = @key)

insert into table (key,...)

values (@key,...)

else

return -1

noeld SSC Guru Points: 96590 More actions · Answer 5

quote:
You can try to do something like this:
If exists(select * from table where key = @key)
insert into table (key,...)
values (@key,...)
else
return -1

in a highly transactional enviroment a connection could insert the @id that the exists query is checking AFTER the check and BEFORE the insert. That's why you should NOT splitt the query into several if you are not using explicit Transactions!!!

* Noel