Jeff Boyce please see below

[NIP]

I think I am following you. Let's see:
In the participant table I should put a field called
rankdiscripID, rankID, and rankdateID, correct?
Now these will all be numbers because they are all auto
numbers but auto numbers have no duplicates while the
number, long integer that I put in the participants will
have Yes duplicates ok checked?
Then how do I get the number say of the date into the
participant table? Each participant should have one of
every entry in the fields of all the tables so working
with the one table (dates) may simplify my retention at
this point.
Do I make a form say called participant rank dates and
include a participant number and the field for the rank
date?
Thanks oh yes and one other thing, do I have to set up any
type of relationship between these tables and if so (using
dates as example) how would I accomplish this?
Thanks again.

-----Original Message-----
It sounds from your description that your "rankings" could be considered
"attributes" of your participants.

If you have participant info in a participant table (say, ID#, [Start date],
FirstName, ...), why not have the ranking info there too?

Keep your (lookup) ranking criteria table, and add in fields to your
participant table to hold the key/ID from the other tables. What ties them
together is considered a primary key - foreign key relationship -- the
ranking tables have primary keys, which, when entered in the respective
fields of the participant table, serve as "foreign keys", pointing back to
the respective rows in the lookup tables.

Or have I misunderstood?

--
Good luck

Jeff Boyce
<Access MVP>

.

..

 

[Jeff Boyce]

Tried twice to respond - email bounced.

Yes, Duplicates OK means more than one participant could have the same
"rank" -- is that what you want?

I don't understand about "date" -- date of what?

Tables store data, forms display data.

Relationships are optional.