Separate tables, because you should be relating those tables to your "main" tables in the DB. For example, for a user database where you also store the user's state, you might have a DB design like:
Users xState ------------ ------------- UserID (PK) |------xStateID (PK) Username | Abbreviation ... | State xStateID (FK)----| ZipCode So, instead of storing the 2 character state abbreviation in your "Users" table, you store the numeric ID xStateID. -- Mosh Teitelbaum evoch, LLC Tel: (301) 942-5378 Fax: (301) 933-3651 Email: [EMAIL PROTECTED] WWW: http://www.evoch.com/ > -----Original Message----- > From: James Blaha [mailto:[EMAIL PROTECTED] > Sent: Friday, March 21, 2003 2:40 PM > To: CF-Talk > Subject: Just wondering Lookup Tables > > > Hello All: > > Just wondering what you all do out there for application lookup tables > for dropdown selection options. Do you use one table for all your > dropdowns and classify them or do you make a separate table for each > dropdown? I’m not sure what the best route to go is. > > For example a state lookup, or a list of options like select one > of 20 cars. > > Regards, > James Blaha > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4