Ouch! that hurts!
Deleting the parent record that created the child...
Fature request to filemaker - show the relationship graph type (one to many, many to one etc) within this dialogue box, between the two tables!!
Glad you worked it out. Since there is NO premium on storage space today and a huge premium on data, let me suggest a concept shown to me by another developer. To avoid actually deleting records, a "Hide" condition is created.
Create two fields in each of your tables. One is a calc field call "One" Value = 1 and the other is a number field called Hide.
Lets say you have an invoice Table and a line items table. You want the user to "delete" line items when a mistake is made, but you want to make sure nothing gets deleted by mistake. Create a relationship between the tables where one of the joins is Hide(Line Items Table) not equal One (Invoice table)
Create a button that sets the value of "Hide" to 1 in the line items table. This breaks the relationship and appears to remove the item from the invoice without actually deleting any records.
Imagine what can happen when an employee gets ad and decides to delete a bunch of mission critical data. You may have back ups, but depending on transaction volume, losing an hour's work or worse can cause havoc.
In the system I created, the only person who can actually delete a record is me.
It's good solution. Also I use the security->PrivilegeSet-> View record if not (value).