Hello - I have a file that has a few related tables. When a user deletes any records (not even all) in one table, it deletes all of the files in a related table, but the delete option in the relationship is not selected. The same option in FileMaker 15 does not delete the related data. Any one else having this issue?
Thank you,
Laura Bowyer
SolutionMakers, Inc.
And you can have a "chain" of these where deleting a record in Table A deletes related records in Table B which in turn deletes related records from Table C, which may make it harder to spot if you are only looking at relationships between Table A and Table C....
Thank you Stephen and Phil,
The strange thing is that it doesn't delete on FileMaker 15??
I'll run through Base Elements but we should never have anything that has
cascade deletes.
Have you tested the current file with both 15 and 16 NOW, or just stating that back when you had 15 before 16 the delete didn't cascade?
The first, different result in different version but on the current file would suggest a bug. But differences in the file due to a mod over time is what I would expect as the usual cause for this type of change.
Yes – I’ve opened the same file today in FM 15 and FM16 and see different results.
Thanks,
Laura
Hosted, local or both?
Local and hosted.
Sure sounds like a Bug to report to FM engineers. They may request a copy of the file after you report it.
Yes. Definitely an issue. I'll post and send a file.
Thanks!
Laura Bowyer
~~~~~~~~~~~~~~~~~~
Sent from my iPhone- please excuse any typos!
I too have been suffering from 'cascading deletes' without a X relationship...grrrrr...
Your observation to look at other 'non related' records was exactly right. Why? Who knows.
All I can say is 'thank you for your comment', it put an end to 2 days of pulling my hair out!
(In my case, the delete would cascade when deleting records from my Members table but I had
a Members TO called FormLtrMembers that had the delete when... checked... Why does FM look
outside the designated table for the 'cascade' switch?)
Thanks
signed grateful for your idea... but perplexed
Ron
TOs are simply instances of a Table in the relationships‘ interface. The Table itself is linked to the other Table(s) via relationships, all of which have to be honored in any actions such as deletions. The relationship graph is simply an interface for controlling the relationships, not the actual file structure.
Glad you found the issue and got it back under control.
Check ALL relationships involving ANY T.O. for these base-tables for the delete option. It need not be on the specific TO-relationship for the current layout(s). It's there somewhere...