Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2000-09-12 : 00:11:39
|
Josh writes "I know there is a post about this, but i have a different twist.
I'm using SQL 7.0.
When you trap the error and print 'error has occured' or something to that nature the system error still precedes it. Is there any way to completely surpress the ugly message and replace it with mine? My users are running Access97 and they don't like seeing a message box with
"ODBC Call Failed"
followed by
"Violation of PRIMARY KEY constraint 'PK_xx'. Cannot insert duplicate key in object 'xx'.
The statement has been terminated." + anything that I Printed.
I know your thinking "Why doesn't this guy just write stored procedures that don't bug out?"
This particualr stored procedure is supposed to mimic the Access Update query which allows you update just the rows that can be updated and skips over rows that cause problems. Thanks." |
|
|
|
|
|
Error Trapping