I guess I can just reply to the post to add another screenshot..
Can you post a screenshot of the relationship definition of the Issues -> ScratchPad relationship?
Although it's probably nothing to do with this, I'm curious why all the other relationships link by IssueID, except that one.
I posted 3 screenshots, the first one being the Relationships definition screen. Maybe I am not understanding what you are asking for ?
What button action or script is assigned to the Delete Scratchpad Entry button on your layout? Is that what you are clicking that is deleting all of these records?
Looking at the layout, it looks like you've added a field from Scratchpad to your layout, which is based on some other table than scratchpad--presumably issues. This suggests that you are trying to delete a scratchPad record by using Delete Record to delete it. But that menu option will delete the current record from the layout's table---Issues, not scratchPad. Once the Issues record deletes, any cascading delete options specified between issues and the other tables in the relationships--what Sorbsbuster is requesting to see a screenshot of, will kick in and delete the related records in those tables.
You'll need to modify your method for deleting a scratch pad record (use a script and/or a one row portal), or since you are only interacting with a single scratch pad record for each issue record, just clear the contents of this field instead of trying to delete the record.
I think you are correct. I will just have a script "clear" the content of the ScratchPad field, rather than delete the child record from the ScratchPad.
I was just using the Button Setup action "Delete Record/Request", I thought it would delete in the context of the SratchPad layout only. I was wrong. Since this ScratchPad field is not a portal, I can't use "Delete Portal Row".
I guess there is no Button setup action to delete only this child record...
Thank You for you help
You don't actually have a "ScratchPad Layout". You have an Issues layout that contains a field from ScratchPad. And this is why delete record deletes the Issue record.
Since it apppears that you can only have one related record in ScratchPad for a given issue, do you even need that table? Given what I see here, it seems you could simply include the fields now present in ScratchPad as fields in the Issues table. But please note, that many databases would use a portal to a Notes or ScratchPad table so that the user can record a series of distinct notes about a given issue so that they can work with those notes as individual, dated or timestamped records instead of one large text field with numerous entries all entered into the same field.
Well said. I am somewhat new to FileMaker and am using the wrong terms. Thanks for the tip, I think I will get rid of the ScratchPad tab, and include it in Issues.