If a record can't be deleted in a bound Microsoft Access 2003 form because deleting it conflicts with a referential integrity constraint in the linked SQL Server table that the form is bound to, the record doesn't disappear from the screen and a message appears to tell the user. However, if there's an INSTEAD OF DELETE trigger on that table and the record doesn't get deleted, the record still disappears from the form even though it still exists and there is no error message. When you close the form and re-open it the record comes back. Is there any way for the SQL Server trigger to return a value that signifies to the client application (in this case Access 2003) that the record didn't get deleted?
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.