> Another example I made my own: > Table FATHER (FATHER_ID,...) > Table CHILD (CHILD_ID,FOTHER_ID,..) > Let's say we have a rule that we send an amount for each child over 18, > otherwise to their father, so:
Can't you do like this? CREATE TABLE Recipients ( RecipientID INTEGER, + BirthDay DATE, + FirstName TEXT(20), + LastName TEXT(40), + ParentID INTEGER ) In this case, ParentID points back to a RecipientID in the Recipients table. If the Recipient is a father, the ParentID field is NULL, otherwise it points to the father. (Or, you can just have a field RecipientType, which says whether it's a father or a child). -- Larry Lustig www.larrylustig.com ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
