Re: Bad idea?

I like users to enter their data through pick lists so the data is consistent. If I let them enter free hand (e.g. textbox) you end up with Chrysler, crysler, crisler, crislyar etc. So I don't just build pick lists from select distinct field from table, I prefer to have a table for each pick list (or in this case combine them into one table.)

100 is probably closer to 10-20 when i
think about it! 10-20 pick lists/combos does not sound very much but if you compare it to my main entities, of which i have 3 or 4.....

cheers
stu

"John Van C" <jvanc_at_pandora.be> wrote in message news:tdmS8.52467$ud.7315_at_afrodite.telenet-ops.be...
> 100 that's quite a lot.Why's that?
>
> "Stu" <smcgouga_at__at_yaho.com_> schreef in bericht
> news:1025091770.26426.1.nnrp-12.c2de0ffb_at_news.demon.co.uk...
> > Is the following a really bad idea? I want to reduce the number of
tables
> > in my database to make it easier to understand.
> >
> > I am building a vb application over MS Acess. I am going to put all
> values
> > for all combo boxes/pick lists in one table. eg:
> >
> > tblList_Names
> > ID ListName
> > --- ----------
> > 1 People
> > 2 Car Models
> >
> >
> > tblListEntries
> > ID ListNameID Value
> > --- ------------- ------
> > 1 1 Bob Brown
> > 2 1 Stella Boy
> > 3 1 Tom Smith
> > 4 2 Ford
> > 5 3 Crysler
> >
> > If I don't do this and I create a table for each combo/pick list I will
> end
> > up with 100 ish tables with 10 values (avg). This way I will have 1
table
> > with 1000 values. I usually like to keep my tables normalised, but on
> this
> > case I think I could do the above. This will also make it easier for
> users
> > to add/edit/delete values that appear in combos/picklists. What do you
> > think?
> >
> > Cheers
> > stu
> >
> >
> >
> >
> >
> >
> >
>
>
Received on Thu Jun 27 2002 - 10:08:26 CEST