[AccessD] Composite Unique Key in 2010

[Gustav Brock]

Hi Susan

I'm impressed. That was special.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD [mailto:accessd-bounces at databaseadvisors.com] På vegne af Susan Harkins
Sendt: 13. marts 2015 19:56
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] Composite Unique Key in 2010

You know, I almost didn't mention it!

Thanks!
Susan  H.

On Fri, Mar 13, 2015 at 2:52 PM, Charlotte Foust <charlotte.foust at gmail.com>
wrote:

> Susan, you nailed it.  Heaven knows why Access decided to mash the 
> dialog box together like that.  That was certainly  no need, but there we are.
>
> Charlotte
>
> On Fri, Mar 13, 2015 at 11:48 AM, Charlotte Foust < 
> charlotte.foust at gmail.com
> > wrote:
>
> > Susan,  that's an interesting thought.  I do have my display set to 125%.
> > I'll try setting it back to 100% and see if that changes anything.
> >
> > Thanks,
> > Charlotte
> >
> > On Fri, Mar 13, 2015 at 10:46 AM, Susan Harkins 
> > <ssharkins at gmail.com>
> > wrote:
> >
> >> Charlotte... I wish I could remember the particulars on this, but I 
> >> remember a situation where properties didn't appear to be available 
> >> because of the size of the dialog! Instead of shriking everything  accordingly, it
> >> just didn't display the properties. Probably not your problem, but thought
> >> I'd mention it.
> >>
> >> Susan H.
> >>
> >> On Fri, Mar 13, 2015 at 1: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