"DavidG" wrote in message
...
Hi,
I'm building a database of horse racing information. One of the fields
I'm
considering as a Key field is Date - RaceDate. One date has many races.
Is
a Date field a wise choice as either a primary or part of a composite?

It seems to be a natural choice in this situation, but I've heard some
awkward stuff regarding the use of dates. Is this just hoodoo voodoo, or
is
there any substance to an argument that advised against using dates?

Thanks
David G

I don't have the time to give this a huge amount of thought but I find
myself asking what other attributes "RaceDate" would have. It would seem to
me that it is an attribute of "Race Meeting". I don't see a 1:M there.
What I see is "Race Meeting" as an entity and one of its attributes being
"meeting date". There might then be a 1:M on "race time" since each meeting
can have many races.

I'd just use numbers to link the two.

Just my 2p worth. Horses for courses.

Keith.
www.keithwilby.co.uk