First, you want to make sure you understand your table relationships and which tables need rows deleted. For example, your Clients Table and your Products Table are likely used in multiple Transactions. So when you delete any particular transaction you would not want any referenced rows from either of these tables to be deleted - it would affect all the other transactions related to that Client or that Product.
Having said that, the key to performing a cascading delete is to use the "Is part of" property on the Child's Ref column to the Parent - I refer to it as a "tightly coupled" parent/child relationship.
To establish this in your example, in the TransactionProduct Table, you would turn on the "Is part of" within your Ref column to the Transaction Table. That's It! When you delete a transaction, then ALL related TransactionProduct rows will automatically get deleted as well!!
For illustration, let me take this one step further...
Let's say you wanted a setup so that if a Client is deleted, then all Transactions and all TransactionProduct entries area also deleted. Not only would you turn on the "Is part of" property in the TransationProduct table, but you would also turn the "Is part of" property in the Transaction Table within the Ref column to the Clients Table. Now, when you delete a Client, all associated Transaction rows are deleted and all TransactionProduct rows are also deleted. But Products would NOT get deleted.
I hope this helps!
LinkedIn
Twitter
