>
>
>I'm not sure if normalisation has much to do with this. It is just the way you describe your database. In stead of identifying a lookup for every case you identify an identity called 'lookup table' which has numerous relations to other tables. I could get a NF3 design with both seperate tables as with one big lookup table. It is just a different matter of abstraction of the problem.
>
>A big lookup table makes sense in a lot of cases.:
>- Performance: Only one file, one buffer, one file handle.
>- Easier to add another lookup (just another identity value)
>- Simpler database design (Obvious when you have in like my cases about a 100 different lookup tables)
>
>However you should keep in mind that if you need to record more data of a particular lookup, you probably have to move the lookup from the lookup table into a seperate table.
>
Hi Walter,
Thank you very much for your input.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
