George said:
Under what circumstances do you think one property would ever *need* to take
precedent? They will always remain separate entities.
AFAIK, related fields don't "share" properties (just common values). In
other words, both sets of properties need to be set.
Let me add a stylistic comment here...
To keep the keys easy to identify, I normally define a primary key for a
Table to be just one field (though Access permits them to consist of
more than one field), and I give the field a name formed by appending
"ID" to the Table's name, such as [XxxxID] for the primary key of Table
[Xxxx].
To foreign keys I give the same name that they have in the Table where
they are the primary key; if I need to refer to a record in the [Xxxx]
Table, I do it using a field that I call [XxxxID] in the Table referring
to [Xxxx]. Access will allow you to use any valid field name for
foreign keys, but if you define a Query that invokes two Tables that
share a linking field, Access will notice this and set up the link for
you automatically.
-- Vincent Johns <
[email protected]>
Please feel free to quote anything I say here.
