Database Design Idea

On Mon, 27 Jul 2009 13:14:00 -0400, "Gina Whipp"
wrote:

John,

In one case I have no choice because the Client INSISTS they have the
ability to do! (I am refering to once Client in particular) and of course,
he pays when he *messes* the database up which is a routine with him bit
that is another story. Then there was the case where data that was brought
in form another source with matchind PK's to the existing data and I had to
run some update queries to change the PK's so I could get it into the table.
(I told them let's try not to do that again.

But other then that NO, NEVER, have you lost your mind... Okay I go
overboard. I just got in the habit of doing it that because of the above
scenarios. And since doing it that way never *hurt* anything I never
stopped. Of course in my latest adventure I set the PK as Autonumber and
gave them a *make-believe* PK because they wanted to edit it and I'm seeing
how that goes... The don't have a Purchase Order number until AFTER the PO
gets approved for ordering.


Sure, that's absolutely a good use of a "natural key". I do tend to put about
three rows of barbed wire and a deep ditch around any way to let users edit a
PK though.
--

John W. Vinson [MVP]