[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.

> Lambert

>> -----Original Message-----
>> From: Lawhon, Alan C Contractor/Morgan Research
>> [SMTP:alan.lawhon at us.army.mil]
>> Sent: Wednesday, June 02, 2004 8:51 AM
>> To:   'Access Developers discussion and problem solving'
>> Subject:      RE: [AccessD] OT: The Great Primary Debate
>> 
>> Martin, Susan, John, Jim, Charlotte, Drew, Gustav, et al:
>> 
>> I think there is another factor involved in this "AutoNumber versus Natural
>> Key" PK debate.  For lack of a better word or terminology, I'm going to
>> refer to it as the "Fear Factor" or a fuzzy type of generalized apprehension.
>> This "apprehension" boils down to something along the lines of, "Well, what
>> happens if the AutoNumber field gets corrupted or somehow those autonumbers
>> get jumbled or out-of-sequence?  If that happens, then how do we re-establish
>> the primary keys and make sure they're associated with the correct records?"