Re: LookUp TABLE(s)

Roy,

We have a bunch of small ( <one db block ) lookup tables, because the legacy system we converted from had it that way. However, in hindsight, it would probably been advantageous to put them all into one big table, with a primary key column being the table identifier.

This would have enabled more generic lookup code, and would have saved a bunch of disk space, and would have cut the total number of tables maintained in half.

Be careful if you lump a bunch of them into one--if you use forms list-of-values, make sure your new setup can be accomodated.

HTH
Steve Cosner

In article <4as7g7$llh_at_newsbf02.news.aol.com> roywagner_at_aol.com (Roy Wagner) writes:
>From your experience (of from something you have read), for a
>Client/Server application, would it be better to have 10 small similar
>lookup tables or ONE large table with a flag column to get the proper
>records. Note that if one table were used, not all the columns would
>contain data, some columns would be specific based on the flag values.
Received on Sat Dec 16 1995 - 00:00:00 CET