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?