Help with Database design:
I am trying to decide whether it is worth building
a database out of my 2.6 DBF tables or just leave
them the way they are now (free tables) because of
how they are currently indexed and related.
We'll forego the app's jargon (horse racing) and just
say sires=Dad, dams=Mom and ID=the horse's number which
is unique.
-------------------------------------
Master DBF table = NAMES - fields:
ID (indexed, tag=ID)
NAME (indexed, tag=NAME)
DadsID (indexed, tag=DadsID)
MomsID (indexed, tag=MomsID)
...other fields
Ex:
ID NAME DadsID MomsID Sex
1234 Something Royal 9946 1854 F <--- mom
9824 Secretariat 4470 1234 M <--- child
8339 No Third Chance 5722 1234 F <--- child
The MomsID (or DadsID) field can show duplicate values.
Because of the duplicate values in MomsID and DadsID
...and the SET RELATION in Fox, I kept separate DBFs
for the Parents (and their names).
-------------------------------------
Statistical DBF table = STATS - fields:
ID (indexed, tag=ID)
STAT1
STAT2
-------------------------------------
Family Tree DBF table = FAM - fields:
ID (indexed, tag=ID)
FN
-------------------------------------
Master DBF table = DADS - fields:
DadsID (indexed, tag=DadsID)
NAME (indexed, tag=NAME)
-------------------------------------
Master DBF table = MOMS - fields:
MomsID (indexed, tag=MomsID)
NAME (indexed, tag=NAME)
-------------------------------------
see next msg...
John Morga
Sr. Manager Information Systems
Applications Development Group
Systems Engineer
Telephonics Corporation
http://www.telephonics.com