Table design -PKs

[Junior]

Hi - Have an mdb with [tblApp] to store applicant records.
The PK is autonumber AppID - AppID has a 1:M relation with many other
tables.
Other fields in [tblApp] i'm concerned with are
SSN-string, AppDate-date
Current table design allows duplicate records with same SSN and
AppDate.(not wanted)
If i set PK on SSN and AppDate to eliminate duplicates, then i can't also
have AppID as a PK.

So, whats the best way to design this table?
if [AppID] is not a PK will that affect all the 1:M relationships?
Thanks -

 

[Harlan]

Instead of setting the SSN and AppDate to a PK...set them to an INDEX....
With the table open in design mode, click on the INDEX button on the toolbar
(the one with a lightening bolt look). Create an index name at the bottom of
the existing index list....then place SSN and AppDate in the Field Name
block... Set this index as Unique...should work for you..

NOTE: If you already have info in the table, it must comply with the
uniqueness or you can't set the index (I believe)

HTH
Harlan

 

[Junior]

Harlan - i'm halfway there - how do you put both fields into the field name
on the index dialog box

 

[Junior]

Harlan thanks - I found some help in Acc97 help - and created the multiple
index..
hate Acc2K help

 

[Joe Fallon]

"hate Acc2K help"

As you should.

A2003 finally made some big improvements to Help.
The MVPs raised a big fuss over this issue and MS listened.