MS Access - Trying to intercept SQL Server unique index error with error-trapping

I dropped a unique index on an INT column in a SQL Server 2008 table.  The index does its job, but it would be nice to present the Access 2007 front-end user with an error message that's a little friendlier than the following:

"Cannot insert duplicate key row in object 'dbo.blabla..' with unique index 'Idx_blablabl'. The statement has been terminated at..."

I could put a little code under the hood in Access under the corresponding field's Before_Update event to check for unique values, but I'd like to simply error trap the error thrown by SQL Server.  Suggestions?
jdanaAsked:
Who is Participating?
 
danishaniCommented:
You may look into below similar thread, to find your answers/ methods for doing so:
http://www.sqlservercentral.com/Forums/Topic300275-131-1.aspx

or when using an ODBC:
http://support.microsoft.com/?id=209855
0
 
jdanaAuthor Commented:
Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.