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.



--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

"John W. Vinson" wrote in message
...
On Sun, 26 Jul 2009 21:52:46 -0400, "Gina Whipp"

wrote:

John,

Thanks for the tidbit. I have never had a problem but then I rarely use
Autonumber and normally I want my related records updated when editing the
main table. BUT you bring a good point I am passing on advice without
taking into consider that everyone doesn't program like me...

Do you (routinely) edit the value *of a primary key field*? OK, I'll trust
you
- you know what you're doing! - but it's something I'd NEVER let my users
do.

Of course cascading updates applies only to editing that field; you can
edit
other fields in a parent table without CU getting into the mix.
--

John W. Vinson [MVP]