[AccessD] Composite Unique Key in 2010

Charlotte Foust charlotte.foust at gmail.com
Fri Mar 13 12:45:03 CDT 2015


@David, I always use autonumber PKs.

In this case, when you try to create a composite unique key--and yes, I
know well how to create them--you can set up the composite key, but the
options to set the Primary, Unique, and Ignore Nulls are grayed out, even
for the Primary key when it's compound.

It has to be something in the way their Access is set up, and this was
migrated (by me) from 2003 mdb to 2010 accdb.  I've never encountered this
in other 2010 setups, so I'm baffled.

Charlotte

On Fri, Mar 13, 2015 at 10:37 AM, Gary Kjos <garykjos at gmail.com> wrote:

> I don't have a 2010 machine here at the office but it does seem to
> work in 2013. Are the properties just not visible at all?  Or do they
> not allow changes?  In 2013 if you are not positioned on the first of
> the fields in the multiple fields indixt - the one with the NAME of
> the index in it, the properties "Primary", "Unique", and "Ignore
> Nulls" go away but if I click in the row with the name they come back
> and allow me to change them.
>
> On Fri, Mar 13, 2015 at 12:29 PM, David McAfee <davidmcafee at gmail.com>
> 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
> >>
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list