Composite Keys in Databases are they GOOD

[Jamesy_007]

So I have this table let's call it tblpersons for this forum. But tblpersons has many fields that i can break into two or three tables, tblpersons has some basic info about the person FirstName LastName , DOB Adddress Phone etc. However there's some other information I want to have but my table will have too many fields in my opinion so I've created another table tbldescrpition where i can have their Height, Weight, Adress_2, FamilyContact etc and the fields go on. I want to have a Primary & Compoiste keys in tbldescription because I don't want duplicate info even with persons with same name i want to be assured that John Zoo ID#2 in tblpersons is definitely same in John Zoo ID#2 tbldesciption so they're linked. Can i do this by having a composite key in tbldescpition and linking the two table with a one to one relationship???, am I going about this the right way can someone guide me through this please???; want to make sure these two or three tables are definitely linked and there no pseudo duplication.

[ranman256]

Don't overwork it, just create an autoNum ID field.
then you only need this 1 field to bind the sub table and need no vb.

[CJ_London]

also little point in splitting a table to create multiple tables with one to one relationship unless there are security reasons for doing so or really are too many fields. Depends what you mean by too many fields but a table can have 255 fields.

Fields where you need to keep a history (perhaps change of address or weight) or there are multiple options (such as landline/mobile/email/mobile#2) you would put into a separate table anyway.