Error handling

[kabirpatel]

I have recently upsized an Access database to SQL Server. The .adp is for the most part working fine.

However, when an end user tries to create a duplicate record in one of the Primary key columns of a Form he gets a SQL Server error message as follows:

"Violation of Primary Key constraint. Cannot insert duplicate key in object myTable".

This is obviously not a very useful error message. What would be the best way to ensure that a more meaningful error message is returned?

I have considered adding code to the "After_Update" event of the cell in question. This however seems long winded. Is there an easier option?

Thanks
Kabir

 

[JoeAtWork]

I tend to be proactive about validation, i.e. do all the checks before-hand rather than wait to see what errors the database returns. In this case, I would check to see if the ID already exists and return a user-friendly message if it does.

If you have some sort of "Save" button you could do this in the function the button calls. If you entirely rely on binding, a likely place to put it is in the form's Before_Insert event.