if there's a one-to-many relationship between Divisions and Departments (one Division has many Departments), it's generally considered good form to have two tables...one for Division and one for Department), where DivisionID is a primary key in the Division table, and a foreign key in the Department table (see the diagram in the tutorial that shows this relationship between tblAuthor and tblBook).
You don't necessarily have to break it out into two tables...but doing so would reduce repetitive data (e.g. having to store a Division name 'n' number of times in the single table model vs. storing it once in a normalized model). Saves space and potentially cuts down on data entry errors :) On 7/21/06, Steven Sprouse <[EMAIL PROTECTED]> wrote: > Charlie, > > so in my case, the Division would be the genre, the Department would be the > author, and the sub-department would be the book name, correct? > > In designing my table then, where the genre was entered in the book table, > would I have to write out each division name or should I replace that with a > division ID? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:247288 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
