L
leandro ribeiro
Thanks for the pointer about the design issue. Actually, I should end up
making forms to organize the data instead of making tables with redundant
data. That challenge notwithstanding, let's see if I can learn to set up
relationships properly. If you can tolerate using my example database, I
changed the ID fields so one is NameID and one is RaceID, and then I put a
field in the Race table labeled NameID with the data type set to number. I
still get the same error message. And I get the same error message if I do
the reveres, i.e. put a field labeled "RaceID" in the Name table.
I obviously still don't understand something.
--
Thanks,
Bruce Hartsell
Department of Social Work
California State University
Bakersfield, CA
making forms to organize the data instead of making tables with redundant
data. That challenge notwithstanding, let's see if I can learn to set up
relationships properly. If you can tolerate using my example database, I
changed the ID fields so one is NameID and one is RaceID, and then I put a
field in the Race table labeled NameID with the data type set to number. I
still get the same error message. And I get the same error message if I do
the reveres, i.e. put a field labeled "RaceID" in the Name table.
I obviously still don't understand something.
--
Thanks,
Bruce Hartsell
Department of Social Work
California State University
Bakersfield, CA