VB/Access Referential Integrity
Posted on 2008-10-29
I just set up a relationship in Access between two tables that enforces one-to-many referential integrity. When I tried to delete the parent record from the query window, I was warned that I would leave orphans in the child table, as I should be.
When I run the same query from my VB code, it doesn't delete the parent record (which is good), but it never throws any kind of error telling me I'm about to screw up the database. Is there any way I can have the VB program let me know when a potential violation of referential integrity is about to take place?