Sorry maybe I am not able to explain this. I don't mind CB as-is but what if I put in RI rules for all three Update, Delete, Insert. Delete we already know that Delete of the parent, though CB does nothing, works in deleteing children (and maybe grandchilren, great grandchildren???).
So what about Insert and Update when they trigger, will CB reflect the triggers to the user, sort of a dumb go between, DBC told me and I'm relaying it to you though I dont understand any of it but stop.
<i><font color="#663300"><i><font color="#663300">So it's okay to have the complete RI defined in the DBC and CodeBook will comply with the rules for Insert, Delete and Update?
If so then CB as-is is fair enough because we can get the RI handled correctly.</font></i>
Codebook doesn't comply with the rules; they happen inside the VFP data engine. Codebook has no control over the DBC.
</font></i>
Regards
Bhavbhuti
©2002 Bhavbhuti Nathwani |
