Razzak or anyone else, I am writing an interior design program. Would it be over-kill to have multiple foreign keys:
customer- primary to project foreign to room/transaction header/transaction details project- primary to room foreign to elements/transaction header/transaction details a quick search could come up with each details. Thank you, Boyd ---- "A. Razzak Memon" <[EMAIL PROTECTED]> wrote: > At 05:24 PM 4/28/2008, [EMAIL PROTECTED] wrote: > > >Razzak, > > > >I did read your article so for a primary key: > >not null or dup. value > >enforces constraints, > >use instead of rules > >builds an index. > >So all others will be foreign keys. > > > >Correct? > > Very correct, Boyd! > > To further understand the PK-FK relationship and a typical > relational database model, take a look at the latest RRBYW14. > > CONNECT RRBYW14 > > At the R> Prompt: > > SET LINES 0 > LIST PKEYS > LIST FKEYS > LIST CONSTRAINTS > > Very Best R:egards, > > Razzak. >
