Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2014

    Unanswered: Problem with table relationships - Foreign Key and Primary


    My application is a series of checklists, represented each by a table. They all have a common "Job ID" which is entered by the user in the first form/table. This "Job ID" is a common value with all other tables.

    What I want, is that the user doesn't have to enter the "Job ID" every in every form. I just want him to enter it once in the first menu, and then it's copied automatically to all the other tables (creating a new record in each table)

    Is that possible? or I'm thinking wrong?

    Thanks for your help and time.


  2. #2
    Join Date
    Nov 2004
    out on a limb
    Provided Answers: 59
    so create a 'master table', lets be creative and call it jobs, store everything that is pertinent to the job in that table, eg the date, the person, the whatever (phase of the moon )

    then make all your individual checklist tables 'child' tables to Jobs, using the primary key of Jobs as the primary key of each table using a one to one join

    when it comes to laying out your form:
    the jobs table acts as a master forj, and how you implement the checklist tables is up to you.. personally I'd probably use a tabbed layout but anything is possible

    but you will need to design each child form first, then embedd those child forms into your parent form making certain the primary keys are correctly identified.

    but before you do make certain you actaully need as many sub tables reresenting checklists

    this design works if you have multiple checklist for the same job,
    or one checklist per job (ie suer selects a specific checklist)
    but it wont handle multiple checklists of the same type for the same job (without further refinement)
    I'd rather be riding on the Tiger 800 or the Norton

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts