[AccessD] Duplicates on Two Values

You can still create a unique key on those two fields without making it the primary key.

Charlotte Foust 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hollis, Virginia
Sent: Wednesday, November 18, 2009 10:47 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Duplicates on Two Values

I always do use Autonumbers as PK, but thought putting the Name & Desc as PK would be a way to check for duplicates. I didn't do it that way - I tried it for a bit as a test - but changed it back.

 

********

I think thats what this form is doing, entering the initial items into

the system.

 

I'd recommend using an autonumber PKID instead of using Item Name andItem Desc.

 

Any table/form that needs to store the item in question should store

the autonumber PKID.

 

If the item description changes at a later date, you only have to

change it in one place.

 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com