[AccessD] Composite Unique Key in 2010

[John W. Colby]

LOL.

John W. Colby

On 3/13/2015 1:29 PM, David McAfee wrote:
> <Start of Natural Key VS. Surrogate Key Holy war>
>
>       That's because you SHOULD be using an autonumber Primary key ;P
>
> </Start of Natural Key VS. Surrogate Key Holy war>
>
> Sorry, I just had to... it's Friday :)
>
> On Fri, Mar 13, 2015 at 10:16 AM, Charlotte Foust <charlotte.foust at gmail.com
>> wrote:
>> I'm running into a problem I've never seen before.  When I try to create a
>> unique composite key, the options to check the unique property aren't
>> available.  This is on a client's machine running Windows 7 and Office
>> 2010.  I've never seen this behavior before and it's making me crazy.  It
>> isn't just one table either, it's all of them.  These are new tables
>> created in 2010 on the machine.  It will allow me to create a composite
>> Primary key, but not a composite unique key.  Has anyone run into this
>> before?  I haven't in 20+ years of Access, so I'm baffled.  It's defaulted
>> to a 2007 accdb format if that makes a difference.
>>
>> Charlotte
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> http://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>