>
>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?

even if VFP RI builder doesn't let u do that
u can always write addional rules

>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?

I don't think I would want that behaviour
btw, the it workds the other way around - if u use a table
it opens the DBC

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

the two points u mentioned are enough, IMHO, but
IAC the DBC gives u a central place for maintaining the DB
it also lets u use VIEWs which are a very powerful addition
to VFP
generally the DBC gives u both more power and more control
over your database
I just want to add that the DBC concept is something ALL major
databases have

Arnon

PS
nobody is forcing you to use a .DBC, so if u really don't see the advantages u can still use old fashioned free tables