Well I disagree. We have a listing of traps with the species of animal we
catch in each trap. The user has the combo box to select an animal name, so
that they don't need to retype each time. It makes no sense to me not to
have all the pertinent information (common name and scientific name) in one
place. Perhaps it's 'bad design' from a programmer's point of view, but if
it doesn't give the user what they need then it is pointless.
I apologize. I was being excessively didactic.
Of course, the user should not have to reenter data! But if you are
storing the species name AND the common name in the trapping data
table for every record, you are both wasting space and risking update
anomalies. Suppose you find that a very commonly trapped species was
entered into the Species table with its Latin name misspelled, or some
taxonomist has revised the family and the species now has a new name.
If you store only the unique species identifier in the trapping table,
you now have only ONE record to correct - the scientific name field in
the Species table. If you copy the scientific name into the Trapping
table, then you must track down and correct every single trapping
record involving that species. You say, quite correctly, "have all the
pertinent information (common name and scientific name) in one place"
- and that is *exactly* what I'm proposing. The one place is the
Species table.
What the user SEES is the common name and the Latin name. What's
stored in the trapping data table is the unique key to the species.
That way both the user and the computer can be satisfied.
John W. Vinson[MVP]