That's essentially what I was saying, Teddy just did a better job of articulating the details. (Whether or not you need periodicalissueid and periodicalChildId is a matter of style. I tend not to do that and just use the composite ID's instead.)
On 1/12/07, Teddy Payne <[EMAIL PROTECTED]> wrote: > I would agree with Deanna. That is a necessary step, but then I would > suggest normalizing one step further. > > tbl_Children (childID, ...) > > tbl_Periodical (periodicalID, ...) > > tbl_PriodicalIssue (periodicalIssueID, month, year, periodicalID) > > tbl_PeriodicalChild (periodicalChildID, childID, periodicalIssueID) > > You want to avoid duplicate information about a Periodical, so you create a > table that keeps track of every issue that has been published. > > Now you have a table that will avoid duplicates of periodicals and children. > > Teddy > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:266429 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
