I have inherited an Access database that was originally built in Access 97 and I have converted to Access 2003. It has a main table (Archive_Register) and several lookup tables used in forms but not defined in relationships. I am not going to setup relationships because there are many records that won't meet the foreign key criteria (the data is in a mess).
In any case, there is a natural key for the Archive_Register table, being MRN. However, the users want to be able to add records without entering MRN, but if they do, it must be unique. So I cannot use MRN as the primary key. I have added code to check for MRN uniqueness.
The Archive_Register will not be joined with any other table.
1. Is there any real advantage to introducing an autonumber field and set that as the primary key, just for the sake of having a primary key?
2. If I index the MRN field, Yes(No Duplicates), will the nulls in the MRN field count as duplicates i.e will I lose those records on creating the index.
Thanks
The risk with keeping an open mind is having your brains fall out.
Shaunk
In any case, there is a natural key for the Archive_Register table, being MRN. However, the users want to be able to add records without entering MRN, but if they do, it must be unique. So I cannot use MRN as the primary key. I have added code to check for MRN uniqueness.
The Archive_Register will not be joined with any other table.
1. Is there any real advantage to introducing an autonumber field and set that as the primary key, just for the sake of having a primary key?
2. If I index the MRN field, Yes(No Duplicates), will the nulls in the MRN field count as duplicates i.e will I lose those records on creating the index.
Thanks
The risk with keeping an open mind is having your brains fall out.
Shaunk