Primary key (autonumber)?

  • Thread starter Thread starter keith Bemis
  • Start date Start date
K

keith Bemis

I have used the primary autonumber as the primary key on
my database and on all the subforms (6 all together )
I have used that as the link orkey for each ,,is that the
correct method?
thanks
keith bemis
 
Holy Wars have started over this question <grin>, but I think it is
generally accepted that an autonumber primay key is the preferred method.
Of course, you don't want to link the autonumber primary key of the mainform
to the autonumber primary key of the subform. (Your question COULD be
interpreted that way). The subform table should have a Long Integer field
which links to the primary key of the mainform. (That is in addition to the
subform having its own autonumber primary key.)
 
I have seen samples of PK AutoNbr to PK AutoNbr between
tables, then uses as forms and sub forms. Is there a
problem with such a setup???

TIA
 
I have seen samples of PK AutoNbr to PK AutoNbr between
tables, then uses as forms and sub forms. Is there a
problem with such a setup???
Click to expand...

Yes. IT WON'T WORK.

For one thing, you cannot assign an Autonumber as a foreign key; for a
second, you cannot update an Autonumber field, so having it as the
Child Link Field of a subform will not work; but most importantly, an
Autonumber IS ARBITRARY. If you *could* link them, it would link each
record of your "parent" table to an unpredictable and uncontrollable
record of your "child" table... not particularly useful!
 
Thanks. I have inherited an ACCESS app with poor table
normalization. There are thousands of records with no
primary key in most tables. While reading an old ACESSS 2K
book with accompany CD, I saw a sample of PK auto number
to PK auto number.
Time to rethink my approach.
 
While reading an old ACESSS 2K
book with accompany CD, I saw a sample of PK auto number
to PK auto number.
Click to expand...

If it had a link from PK Autonumber to FK Autonumber, break the CD and
trash the book <g>...
 
Back
Top