Chad,
Are you saying (just wanted to clarify), that according to your database architect, keeping all lookups in one table (for the sake of simplicity), makes sense? (even though strict normalization rule is broken). Do I understand you correctly?
>Dmitry,
>
>You're welcome. As far as strict data normalization goes, separate tables is more appropriate. Knowing this, I consulted our database architect about the decision. After describing the way I would be using the lookup table, he agreed with me that it made sense in this case to break the normalization rules.
>
>HTH,
>Chad
>
>>Chad,
>>
>>First, thank you so much for your input.
>>Interesting, that the way you describe your lookup table is exactly how I have it in my Clipper application. All lookups are in one table. The reason I did it in Clipper is because of the limit of number of file handles. Then I heard, at one of the VFP user-group meetings, by a VFP guru, that it is better (although I don't remember if he said "why") to split all these lookups into different tables. Hence my question here. Now I am a little confused, maybe I should do what you did and what I did in Clipper. I will have to think of all pros and cons again.
>>
>>Again, thank you for your help.
"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
