I have a pair of tables that are linked with referential integrity. I set
the relationship type to "Cascade" rather than "Restrict".
According to the on-line help screens, this is supposed to cause child rows
in the dependent table to be deleted when the parent row in the parent
table is deleted.
In my real daytime job I'm a IBM DB2 mainframe programmer, and I kind of
know what to expect based on the on-line help.
However, I've found that in my Delphi application (Delphi 2.0, Desktop
edition), running against these Paradox 7.0 tables, I get an exception when
I try to delete the parent row--the exception says it can't be deleted
because of the existing child rows.
To work around this, I've coded my own delete of any applicable child rows
before deleting the parent row.
But it doesn't seem like I should have to do that.
Am I misunderstanding the documentation, or have I set up the tables and/or
the referential integrity wrong?
Omaha, NE, USA