I generally use one lookup table for all lookups except those that require
a FK/PK relationship (which can be substituted with rules to the lookup
table if you need them). I usually run with staticdb ON, so yes it is
difficult to add new tables, easy to add more rows to the lookup table. And I
feel
better when I list a database, and there aren't 40 tiny little lookup
tables, often with only 5 to 10 rows in each table. That to me seems like a
waste
of space. And I think it's no more difficult to remember the LookupCode
value than remembering the lookup table name. And I always know the names of
the other columns in this table.
Usually my lookup table has these columns:
LookupCode Text 8
LookupText Text 30
LookupInt INT
LookupDate DATE
LookupDouble DOUBLE
Karen
> Very good points, I prefer your way when I have a choice.
>
> On the other hand, if you have the db locked down with STATICDB, adding
> tables requires you to down the db to add the new tables.
> This make for a different kind of difficulty. depending on your
> situation.
>
> With a master table you can just add data and code it up.
>
> We actually use a mix, using a master table for fairly generic values and
> distinct tables when the data and relationships are elaborate.
>
>
>
> Dennis McGrath
>
>
