Re: Using seek to find if a record exists

>. in the context of the discussion, the suggestion was not to add
>the other field to the existing PK, but to add another PK, which is
>nonsense.
>
>
>2. a compound primary key cannot have Nulls in any of the fields, so
>your candidate compound key would be an extremely poor choice for a
>PK.

1. You are absolutely correct; I used the wrong terminology.

2. Using a Birthdate field as part of a primary key would not be a poor
decision if the birthdate were required for all records. An example of
a situation where a birthdate would be required is a hospital keeping
track of birth rates.

.

Relevant Pages

  • Re: Using seek to find if a record exists
    ... a compound primary key cannot have Nulls in any of the fields, ... >>so your candidate compound key would be an extremely poor choice ... > poor decision if the birthdate were required for all records. ... where the compound key you describe could possibly have been used. ...
    (comp.databases.ms-access)
  • Re: Using seek to find if a record exists
    ... Using a Birthdate field as part of a primary key would not be a poor ... IMO - birthdate is still a poor choice for a primary key. ... nothing but guarantee unique identification of a record. ...
    (comp.databases.ms-access)
  • Re: Table Structure ordering of columns
    ... you're using a compound Primary key? ... Now, when seperate databases are compined, there will never be a primary ... The DatabaseID is the Date and time in numeric format. ...
    (comp.databases.paradox)
  • Re: not allow for duplicate for a combination of two fields
    ... > I did what you said but the clientid on its own is not unique - it is ... Karl did not suggest a compound Primary Key. ... with its unique property set to yes. ...
    (microsoft.public.access.tablesdbdesign)