One answer is don't even try. Make the primary key for that table an
autonumber field.
About now you are rightfully asking "Then how do I prevent duplicates?" Good
question. Sounds like the table might be a bridging or linking table to break
up a many-to-many relationship. In that case make a unique constraint or
index like so:
Open the table in design view.
Go to View then Indexes.
In the first blank row of the Indexes window, make up a name in the first
column.
Next select the first field name in the Field Name column.
After picking the first field name, go down and change Unique to Yes (if you
really want it as your primary key here's your opportunity)
Go straight down the column and pick the next field name.
Repeat as necessary.
You might want to change some of the sort orders, but it doesn't make that
much difference.
Now for the momemt of Truth! Save the table changes. Access will create the
new unique index. Access will also raise heck if you have any data that
violates the unique constraint and won't let is save.
You can check for problem data in advance with a Totals query like below:
SELECT Country.Contact,
Country.Country,
Count(Country.Country) AS CountOfCountry
FROM Country
GROUP BY Country.Contact,
Country.Country
HAVING Count(Country.Country) >1;
If the count of your selected fields is greater than one, that data needs to
be fixed before you can create a unique index (or PK).