[AccessD] "Faked" replication

Um ... I'm lost in the woods.  My understanding was that Access did
recommend GUIDs.  I've never seen anything from them discouraging their
use.  They are a PITA to work with, which is discouraging enough on its
own.  Now I can't figure out who's recommending what??

Charlotte Foust

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Thursday, December 18, 2003 10:51 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] "Faked" replication


Yes -- OK, now I understand the confusion. Thanks! ;) I thought YOU were
saying that MS DID recommend using the GUID's as primary keys. :)

Susan H.


> Hi Susan
>
> By second (forth?) read I now understand:
>
> >> Microsoft discourages the use of GUID as a primary key, but that's 
> >> because most people don't really need universal uniqueness. When 
> >> uniqueness across many systems is vital, however, the GUID datatype

> >> is definitely the way to go. Just remember that you pay a price in 
> >> performance.
>
> I read this HOLE paragraph as one statement from MS. But it is only 
> the first sentence ... the remaining part of the paragraph is YOUR 
> opinion, right? Sorry.
>
> /gustav
>
>
> > I don't remember ever reading that MS suggest using GUID's for 
> > primary
keys,
> > but that may be the case. My reference state just the opposite.
>
> > Susan H.
>
>
> >> Hi Susan
> >>
> >> Oh, you are about to confuse me ...
> >>
> >> Steve talked about collecting data from 15 locations.
> >> You wrote about "uniqueness across many systems"
> >> And MS is quoted for suggesting that "GUID datatype is definitely 
> >> the way to go" in such a situation.
> >>
> >> Then you conclude:
> >>
> >> >> > Microsoft recommends that you not use GUID's as primary keys 
> >> >> > ..
> >>
> >> How does that match?
> >>
> >> /gustav
> >>
> >>
> >> >> Ehh, Susan ... aren't you (re)reading your own articles too 
> >> >> fast:
> >> >>
> >> >> <quote>
> >> >>
> >> >> Microsoft discourages the use of GUID as a primary key, but 
> >> >> that's because most people don't really need universal 
> >> >> uniqueness. When uniqueness across many systems is vital, 
> >> >> however, the GUID datatype
is
> >> >> definitely the way to go. Just remember that you pay a price in 
> >> >> performance.
> >> >>
> >> >> </quote>
> >> >>
> >> >> Isn't "across many systems" exactly the situation of Steve?
> >>
> >> > =============I don't really understand your question? Do you 
> >> > think
the
> >> > statement is wrong? FWIW, I'm not suggesting the article solves
anyone's
> >> > problem. Just linking because it discusses the subject. Arthur 
> >> > may
pipe
> >> > in here later.
> >>
> >> >> /gustav
> >> >>
> >> >> PS: Nice picture of you and your mother!
> >>
> >> > =============Thanks. :) Remember the pic of Ann Landers that was 
> >> > a bazillion years old? Well, she's not the only one that can pull

> >> > that trick.
BTW,
> >> > that's actually my granddaughter. :)
> >>
> >> Perfect! Do I feel lucky?
>
> _______________________________________________
> 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