Primary Key & Data Entry Forms

I am trying to create a database for entries for a dog show the following is
how I have set it up so far
TABLE - DOG_DETAILS - Fields - Registered Name, Breed, Sex, Date of Birth,
Breeder, Sire, Dam, Class_1, Class_2, Class_3, Class_4, Class_5
TABLE - CLASSES - Fields - Class_No, Class_Name (this is used as a lookup in
Dog_Details)
TABLE - SEX - Fields - Male, Female (this is used as a lookup in Dog_Details)
TABLE - CONTACT_DETAILS - Fields - Date of Entry, Title_1, First_Name1,
Surname1, Title_2, First_Name2, Surname2, House_No_Name, Address_1,
Address_2, Town_City, County, Postcode, Telephone_No, Email, Catalogue_Entry
TABLE - TITLE - Fields - Mr, Mrs, Miss, Ms, Other (this is used as a lookup
in Contact_Details
TABLE - REVENUE - Fields - First_Entry (this is always £2.00 per dog, there
can be multiple entries of dogs per exhibitor), Subsequent_Entries (with the
same dog, if selected always 50p per additional entry), Not_For_Competition
(if selected always £1.00), Membership (if selected could be Single £1.00,
Joint £1.50, Family £2.50), Prepaid_Catalogue (tick box if selected the value
which is always £1.50 should appear in field PrePaid_Catalogue_Value),
Total_Revenue
TABLE - Membership - Fields - Membership_Name, Membership_Value (this is
used as a lookup for Table Revenue.

The only constant per entry would be the Registered Dog Name would it be a
good idea to use this as the primary key and link to the other tables using
foreing keys? If not should I use Alan Browne auto number routine? My aim
is to enable data entry into a form (made from the many tables, which I think
I will need a query to build the form?) to produce a database which contains
all the data which can be queried and reported from. Do I build a complete
table in the database which contains all the entered data or let is reside in
the individual tables as setup? I am not very good at linking tables with
relationships.

Any help would be appreciated - Many thanks from this beginner
.

Relevant Pages

  • Re: Primary Key & Data Entry Forms
    ... I would expect that it would at least be worth having next year's show in the same database, as it would save typing many of the exhibitor's details again. ... Breed table (one record for each breed of dog), ... If you don't have an exhibitor entering in multiple shows, you can skip this and use a single table for the exhibitor info and the entry in the show. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Fast File Searching
    ... A database can be extremely fast, because you can load all of those ... ID Filename FieldValue ... 1001.txt dog ... file every time a search request came in. ...
    (microsoft.public.dotnet.csharp.general)
  • Re: Simple question
    ... > can have more than one entrant join an event and any single entrant could ... >> I am working on a VB program that stores entries into a dog show. ... >> each entry can enter any number of 5 events over the weekend. ...
    (microsoft.public.vb.database)
  • Re: Simple question
    ... I would create one table for entrant information, ... > I am working on a VB program that stores entries into a dog show. ... > each entry can enter any number of 5 events over the weekend. ...
    (microsoft.public.vb.database)
  • Database Design
    ... I am trying to create a database for dog show entries from which the base ... SEX (for use as a drop down box lookup for selection) Male, ...
    (microsoft.public.access.tablesdbdesign)