Doug, yYou can actually use a single table for that. One way is to create a field that serves as a "parent_id".
Example: ID: 1, NAME: Antiques and Vintages, PARENT_ID: 0 ID: 2, NAME: Antique Furniture, PARENT_ID: 1 ID: 3, NAME: Vintage Cars, PARENT_ID: 1 ID: 4, NAME: Hutches, PARENT_ID: 2 ID: 5, NAME: DeSoto, PARENT_ID: 3 Hope that makes sense, Doug. Michael > -----Original Message----- > From: Doug Brown [mailto:[EMAIL PROTECTED] > Sent: Monday, August 21, 2006 11:16 AM > To: CF-Talk > Subject: Database design question > > On my classifieds database it will have... > > categories and corresponding sub_categories and corresponding > sub_sub_categories. How would you design the table names and relationships > to avoid confusion? Kinda new to database design!! > > IE: > > Antiques-category > antique furniture - sub_category > hutches - sub_sub_category > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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/groups/CF-Talk/message.cfm/messageid:250492 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
