Need help designing the structure of a form/subform

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ivchisholm
    New Member
    • Mar 2011
    • 8

    Need help designing the structure of a form/subform

    I have a database that has these two relevent tables: "Clients" and "WeighIns"

    "Clients" has these fields: "IDClient", "LName", "FName" and other information not pertinent to this post.

    "WeighIns" currently has these fields: "IDWeighIn" , "IDClient" (linked to "Clients" table), "WeighInDat e", "HT", "GoalWT", "WT", and "BF%"

    I'd like to build a form that allows me to pull up just the identifying information for my client and contains a subform where I can input the client's current height, weight, and body fat information WITHOUT overwriting any previous entries.

    The goal here is to create individual monthly weigh-in reports, as well as reports for annual (to show progress through the year) and all (to show beginning-to-end progress). Also will create a report showing ALL clients and their goal weights and current height and weight.

    I've done forms/subforms before, but keeping in mind my reports that I'll need, my mind is just tied up in knots on how to accomplish all this.

    Thank you, in advance, for your assistance.
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32633

    #2
    We normally help with problems here. This seems like a tutorial to order (Tutorials involve much, much more work).

    I'll give some very basic instructions, but if you need help let us know which bits you're stuck on and we are better able to help.
    1. Design main form for clients.
    2. Design a separate form for WeighIns.
    3. Create a Subform control on your main form and select the WeighIn form as the form.
    4. This works more easily if the two tables are defined as linked in the database relationships.
    5. Ensure that the Master Link Fields and Child Link Fields are set up to link the two tables correctly.


    Good luck with this (BTW your question was quite well explained for a first-timer, so I was happy to cut a little slack on the question).

    Comment

    Working...