How do you trap what I might call "form-level" errors in Access 2000?
You have an Access 2000 form, as front end to your SQL database, containing related tables (say CUSTOMER and ORDER)
You do not want the user to be able to delete a Customer for whom Orders exist - and you set up database-level rules to achieve this.
When the user tries to delete a customer who has existing orders - you get a horrible SQL message that means they cannot do it.
PROBLEM: HOW do you trap this error condition and replace the SQL message with your own friendlier message? (Note: All the normal form EVENTs do not seem to be able to achieve this).
You have an Access 2000 form, as front end to your SQL database, containing related tables (say CUSTOMER and ORDER)
You do not want the user to be able to delete a Customer for whom Orders exist - and you set up database-level rules to achieve this.
When the user tries to delete a customer who has existing orders - you get a horrible SQL message that means they cannot do it.
PROBLEM: HOW do you trap this error condition and replace the SQL message with your own friendlier message? (Note: All the normal form EVENTs do not seem to be able to achieve this).