I am looking for suggestions/ideas on the best way to implement a set of lookup tables. I've considered various options (putting all lookup values in one table, managing multiple lookup tables). I'll try to describe my scenario below. If you have any fresh ideas or suggestions that have worked for you in the past, please either email directly at [EMAIL PROTECTED] or send a reply to the list.
Scenario: I have several lookup tables that will be shared between different sites. I am using a site-id to identify each site. For some tables all the sites will share the same lookup data. However, on some sites one or two of the lookup entries might be different. Here is an example. Occupation ID SITEID DESCRIPTION --- ------ ----------- 1 1000 CARPENTER 2 1000 GOVERNMENT 3 1000 CONTRACTOR Now, site 1000 uses Carpenter for the Description, but Site 2000 might want it to say Craftsmen. So I would add another entry 4 2000 Craftsmen The question is do I add additional entries to repeat Government and Contractor for Site 2000 or do I store data for siteID in a list format and use an IN query as listed here: ID SITEID DESCRIPTION --- --------- ----------- 1 1000 CARPENTER 2 1000,2000 GOVERNMENT 3 1000,2000 CONTRACTOR I have several lookup tables that that are very similar to this example. Thoughts? Ideas? Thanks - Tracy ******************************* Tracy Smith TCS Technologies, LLC Web Development & Programming President http://www.tcstech.net Phone: (888) 318-9840 Fax: (202) 478-0897 Email: [EMAIL PROTECTED] ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
