Hey all,
(Access 2000)
I've been having a horror story with this design problem. My Database is
Structured like This: AUTHORS, BOOKS, PAGES. Those are the Tables and each
Item in each table needs a unique ID# based on its context.
Primary Keys
AUTHORS = AuthorID - NO Duplicates
BOOKS = AuthorID - Dups OK
BookID - Dups OK
PAGES = AuthorID - Dups OK
BookID - Dups OK
PageNumber - Dups OK
So for instance the pages need to number from 1 to <i>n</i> for each Book of
each Author.
The problem I had after I set this up is that from PAGES to BOOKS
I could NOT use referencial integrity because it could not identify a unique
Primary Key, (because I used Duplicates OK = True in BOOKS)
-> Is this not a valid way link a 3 level database?
I tried using auto-number primary keys but that killed the validation for
duplicates in the table.
-> Shouldn't Access treat two(or more) Primary Keys with Dups OK = True the
same as one primary Key with Dups = NO so that I can set up integrity
between tables using these two primary keys?
Thanks for any insight!
~Philip