I have some experince with MS Access, and with most things computer, however I have need of a DB that is beyond my cursory skills. I am trying to design a DB to be used as a Weight Training/Fitness Log.
I have an understanding of VB, but not a working skill set. Similarly, I understand MS Access and can create simple databases with a few tables and forms, but I do not have any of the more in-depth skills required to create a very complex database.
I am using Windows XP, and Microsoft Access 2000.
I know what each record needs to store, but I am not sure how to make it happen. Each record will be unique by date and most of the fields are easy enough. However, in addition to adding fields such as "Goals (memo)", "Cardio (list)" "Cardio Time (number)" "Cardio Distance (number), etc.
The problem is that I also need to be able to add an infinite number of unique exercises to each day's record and each exercise must be stored with its weight, sets, and reps. This creates an infinite number of possible records and obviously I can't create a table with each possible exercise with each possible combination of weights, sets, and reps.
A sample data set would be as follows:
1st Tip Try not to use MEMO feild text feild 255 Should be heaps I have lost 2 database haveing heap of memo ffeilds in then
Looks like a
Table of Users
Table of Goals
Table of Exercise
And a Table to join then
hope this help
See clear as mud
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
Yes, I can certainly fit the contents of those fields into a 255 character text field.
As for the table of users, actually there will only be one "user" as the db is not for multiple users...just me
The won't really require a table because that field is really just so I can browse back through and see what daily goals I've been setting and to provide impetus to meet those goals daily. The data in the "goals" field will be random and not constricted.
I think I will need a table for Workouts (the main table) and a table for exercises, but I don't exactly know how to handle the unique aspects of adding an unspecified number of exercies to the workout table for each day...or if this is even what will need to happen.