Joint Key fields vs PersonID

[FuzMic]

Hi folks

In a Jet table involving people, it is normal to have 2 fields, ie firstName & lastName. For indexing we can have these 2 fields as joint key fields.

Alternatively we can convert these 2 fields into a composite PersonID eg Patrick Cameron can be CP001. (Serial numbering by DMax)

To me, the advantages to have an PersonID are
1 At Combo DropDown, PersonID makes locating & selection easier
2 Similar 1stName + lastName can be resolved with another serial

The questions i always wanted to ask:
1 Is there any advantage to use one method over the other?
2 Is there another way to skin this cat?

Peace

 

[boblarson]

My personal preference? Just use an autonumber for the PK and you can use a Multi-Field index set with No Dups to keep duplicates out. For names dups are going to happen so you'd need another field that wouldn't be possibly to have the same info. Otherwise, it just works fine to have an autonumber PK (remember the ID is really for the system to see, and not for general usage).

 

[FuzMic]

Thanks mate for the sharing. Cheer!