Referential integrity rules ensure that a team which is referenced by other tables cannot be deleted. However, the team is also referenced by entries in the Person Team Member table, which renders direct deletion of a team imposible. So, entries in the team member table have to be deleted before the entry in the team table itself. Attempting to delete the entry in the Person Team table then reveals if referential integrity is violated, in which case the entries in the Person Team Member table have to be restored.
The easiest way to solve this problem is to apply a transaction mechanism. The transaction is begun before deleting the members of the selected team. It is committed after deletion of the team in the Person Team table, if there is no violation of referential integrity rules. Otherwise, the operations are rolled back.
It should be mentioned that, in Access, such user defined transaction processing can not be performed on data used in bound forms, i.e. the recordsets must be unrelated to the record source of a form. Access uses its own transaction management on bound forms ( Getz & al. 1994).