[AccessD] OT: The Great Primary Debate

Hi Lambert (and Mark)

Oh sure, I did get it!

My example was just an illustration - based on a real-life story many
years ago (not my design).

/gustav


> Gustav,

> " Bad design can or will always cause trouble". Exactly. I was not wondering
> how data might get messed up, we all know lots of great ways to do that, but
> just commenting on a flaw in some of the RIDICULOUS arguments people put
> forth for "Natural Keys". 

> In case you didn't get it, I'm in the AutoNumbers Rule class. [Just barely
> 50, so that makes me a slightly old fart to use Colby notation  :-) ]

> Lambert

>> -----Original Message-----
>> From: Gustav Brock [SMTP:gustav at cactus.dk]
>> Sent: Wednesday, June 02, 2004 1:58 PM
>> To:   Access Developers discussion and problem solving
>> Subject:      Re: [AccessD] OT: The Great Primary Debate
>> 
>> Hi Lambert
>> 
>> One way this can happen is if referential integrity is not applied or
>> is not applied correctly; then a parent table can be deleted leaving
>> children data with no clue where they belonged to. But then again:
>> what are we talking about? Bad design can or will always cause
>> trouble. 
>> 
>> /gustav
>> 
>> 
>> > No, I'd say that the answer to this unspoken question is that if they fear
>> > the corruption of the PK field then why on earth are they storing ANY
>> > information in a database at all? If one field can be magically corrupted
>> > then so can all the others.