Forum home » Delegate support and help forum » Microsoft Access Training and help » Access 2007 - Creating Primary Keys
|
|
|
The UK's most regular Training information: See also: |
|
Welcome. Please choose your application (eg. Excel) and then post your question. Our Microsoft Qualified trainers will then respond within 24 hours (working days). Frequently Asked Questions
Any suggestions, questions or comments? Please post in the Improve the forum thread. |
Access 2007 - Creating Primary Keys
Resolved · Medium Priority · Version 2007
Reply Tue 30 Mar 2010, 16:37Delegate Martin said...
Martin has attended:
Access Introduction course
Access Intermediate course
Access Advanced course
Excel Introduction course
Excel Intermediate course
Excel Advanced course
Access 2007 - Creating Primary Keys
Hi,
Using Access 2007/Windows 7 and looking to create my first working database.
Having spoken to Anthony during my intermediate course, it feels as though the Primary Key in my initial contacts Table will be a unique identifier code relating to individuals - something like 2-4 letters at the start followed (upto say 4) digits. E.g. NOTT01 or OFF0150.
So my first question is:
Should I create the unique identifier code as a single field to contain all the necessary text and number, or would it be better to split the unique identifier into its two elementsin two fields? E.g:
CATEGORY of Person (E.g. NOTT or OFF) and NUMBER within the category
Also, if it were split into two fields, is there a way of making the number a separate AutoNumber for each different category of Person or is this a hope too far do you think?
Many thanks
Martin Parker
For upcoming training course dates see: Pricing & availability
RE: Access 2007 - Creating Primary Keys
Hi Martin,
Thank you for your question.
Sorry for the delay in responding.
I suppose the answer depends on whether the entire mix of letters and numbers will be completey unique for each individual which means just having one Primary key holding all the information.
Is all the information held in one table?
Do you have a separate table for the employee and other tables holding the list of categories and numbers?
If you split the fields, the primary key must be the part of the code that is unique to each individual. The second field could be set up so you enter extra info such as Dept. for each individual.
You can then create a query to concatenate the two fields into a new field maybe for reports.
I hope this helps.
Regards
Simon
|