jwcolby
jwcolby at colbyconsulting.com
Wed Sep 26 09:12:42 CDT 2007
>If you had an app with 30 drop downs...would you create 30 separate lookup tables? If I have an app with 10 drop downs for state I would create one state lookup table and use that for all 10 drop downs. If I had an app with 5 different address type drop downs (unlikely) I would create one address type lookup table and use that for all 5 drop downs. Does that answer your question? One lookup table for each "type" or "list" (or whatever you might call these) table. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte Sent: Wednesday, September 26, 2007 10:05 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Mucking around I have seen this before(and used it)...but out of curiosity. If you had an app with 30 drop downs...would you create 30 seperate lookup tables? Thanks, Mark A. Matte ----------------------------------------> From: jwcolby at colbyconsulting.com> To: accessd at databaseadvisors.com> Date: Wed, 26 Sep 2007 09:54:09 -0400> Subject: Re: [AccessD] Mucking around>> The general argument is that you have THREE columns.>> PKID> TypeOfDataID> Data>> The TypeOfDataID might be:>> 1 Cities> 2 States> 3 Name prefixes (Mr. etc)> 4 Address Types> Etc> Etc>> So you might have data that looks like:>> 1 2 CA> 2 2 AZ> 3 3 Mr> 4 3 Mrs> 5 4 Home> 6 4 Work> 7 4 Shipping> 8 1 San Diego>> Thus you have place all of your single column "type of something" data into> a single table with another column which allows you to find only the cities,> or states, or types of addresses or (place your list data type here).>> It works, but it causes headaches, but people do it.>> John W. Colby> Colby Consulting> www.ColbyConsulting.com> -----Original Message-----> From: accessd-bounces at databaseadvisors.com> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins> Se! nt: Wednesday, September 26, 2007 9:42 AM> To: 'Access Developers discussion and problem solving'> Subject: Re: [AccessD] Mucking around>> Except that tables are supposed to store like data, not data that simply> looks similar and happens to have the same structure. I would think the> data's purpose matters more in the decision than the data's structure.>> Susan H.>> LOL. Proper normalization says that it is not necessary. Never the less> there are those who argue vociferously for this method.>>> --> AccessD mailing list> AccessD at databaseadvisors.com> http://databaseadvisors.com/mailman/listinfo/accessd> Website: http://www.databaseadvisors.com>> --> AccessD mailing list> AccessD at databaseadvisors.com> http://databaseadvisors.com/mailman/listinfo/accessd> Website: http://www.databaseadvisors.com _________________________________________________________________ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com