Adding a Numeric Key Field Where a Fabricated Text Key Field Has Been Used

Giganews Newsgroups
Subject: Adding a Numeric Key Field Where a Fabricated Text Key Field Has Been Used
Posted by:  croy (cr…@invalid.net)
Date: Mon, 08 Dec 2014

I'm given an old MS Access mdb that contains several hundred
thousand records, a central table with 35 fields, and asked
to "make it better".  It's already split and secured.

The most central table has a text key field with entries
like F990050CTN.  It is made up of various snips of data
about the record, that is all repeated (sometimes in more
detail) in various fields.

The custodian of this database refuses to let me change this
"id" field.

One thought I've had would be to keep this field, but demote
it to an indexed--no dups text field, and install a new
autonumber key field for the behind-the-scenes
relationships.

My question is, would this serve to speed anything up, or
would it simply add more baggage to the db, and maybe even
slow it down?

Any thoughts appreciated.

--
cr

Replies