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 |
|
gperque
Starting Member
7 Posts |
 Posted - 2007-07-30 : 11:13:53
|
| Hi All,I develop most of my application using Microsoft Access and I use SQL Server 2000 as the backend. If I generate an error in SQL, SQL Server typically passes that error to Microsoft Access as an ODBC error. For example I have this Raise error code in a trigger "RAISERROR ('ECI Status already exists, Insert aborted', 16, 1)". It passes this error to Microsoft Access as an ODBC error.Any suggestions on how to trap these errors.Glenn |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-07-30 : 11:46:08
|
Are you using ADO or DAO as data layer for application?Typically Err.Number will trap any error given.
E 12°55'05.25"N 56°04'39.16" |
 |
|
|
gperque
Starting Member
7 Posts |
Posted - 2007-07-31 : 13:55:59
|
I use ADO. As I think about this problem, it is really not an SQL Server issue. I should post this in a Microsoft Access forum. Anyway, I know I can trap errors that have numbers, but all errors from SQL Server are coming across as ODBC errors. As I stated in my initial message, I have an error coded in a trigger and when that trigger fires Microsoft Access does not display the error from that trigger. It displays an ODBC error.Thanksquote:
Originally posted by Peso
Are you using ADO or DAO as data layer for application?Typically Err.Number will trap any error given.
E 12°55'05.25"N 56°04'39.16"
|
|
|
|
|
|
|
SQL Server Errors