>(Sigh) I guess I just dont get it. I don't see
>how the DBC does anything for me. My tables are
>related on a field that is holding a unique ID
>number that will NEVER change. I could see if the
>table linking info was, let's say, a last name.
>A girl gets married and changes her last name.
>That change would be automatically carried through
>all the child tables...and I tried it...and it works
>great, and that's cool, but none of my data is in
>this situation.
>
>Let's say I SQL-insert a record in the parent
>table that sets the primary index field to some
>value:
>1) Will the database automatically SQL-insert records
>in all the child tables with the same value in the
>related fields?
>2) If I delete a record in the parent will the
>database auto-delete the corresponding data records
>in all the child tables?

yes -- if you tell it to do that. the MS supplied RI code has problems with compound indexes though...

>3) If I say OPEN DATABASE MYDBC will the database
>automatically USE all the tables in the database
>and SET RELA TO all the relationships created with
>the database designer?

no, but when you specify which tables to use in a form, any relationships in the DBC are automatically added to the data environment.

>
>If not, besides the integrity and duplicate record
>control (both of which are not a prob),
>what's the point??
>
>John