View Single Post
  #12  
Old August 6th, 2007, 12:21 PM posted to microsoft.public.access.tablesdbdesign
BruceM[_2_]
external usenet poster
 
Posts: 1,763
Default PK - To AutoNumber or Not To AutoNumber - That is the Question

Then they have a problem that they might have avoided with a more "natural"
EmployeeID used as the key, until they decide that since everybody is part
of one company everybody's ID should be the same format. There is no single
best answer, but having the number format change within a single
organization is probably the more likely scenario.

"Jamie Collins" wrote in message
oups.com...
On Aug 3, 9:56 pm, Jerry Whittle
wrote:
I once had the 'pleasure' of trying to fix a problem where a company was
bought by another and, guess what, the employee numbers were all changed!
Since they didn't have Referential Integrity enabled (actually couldn't
as
there were some orphaned records) couldn't use Cascade Update.

I'm a firm believer in autonumbers for PKs. If it doesn't have a meaning,
you won't be tempted to change it.


Now consider the scenario where two companies use auto-increment
values for their personnel data then those companies merge...

Jamie.

--