|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
December 24th, 2007, 08:46 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
How to normalize this table
I have created asmall application in vb.net. Not relevent here I know , but
the table structure of one of the tables is. Right now I have three tables, tblPatient, tblGlucose and tblExercise. I need to come up with a better solution for the exercise table. Right now I just update the table for everyday. Right now the records are kept based on the WeekBeginning field, so I want 7 records before I start a new row. The weekdays in the table are to give the user of the application a visual sense in the form of when they have exercised. Any suggestions? tblExercise ExerciseLogID PatientID WeekBeginning DateEntered ExerciseYes ExerciseNo MinutesExercised Sunday Monday Tuesday Wednesday Thursday Friday Saturday Walk Jog Run Swim Bicycle WhyNot WeeksTotal -- Thank you very much CoachBarkerOJPW 
|
|
#2
December 24th, 2007, 08:57 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
"CoachBarkerOJPW" wrote in message ... I want 7 records before I start a new row. There's one problem. Use a separate record for each day's readings rather than seven readings in one record. To normalize, think long rather than wide. Tom Lake
|
|
#3
December 24th, 2007, 09:54 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
On Mon, 24 Dec 2007 12:46:00 -0800, CoachBarkerOJPW
wrote: I have created asmall application in vb.net. Not relevent here I know , but the table structure of one of the tables is. Right now I have three tables, tblPatient, tblGlucose and tblExercise. I need to come up with a better solution for the exercise table. Right now I just update the table for everyday. Right now the records are kept based on the WeekBeginning field, so I want 7 records before I start a new row. The weekdays in the table are to give the user of the application a visual sense in the form of when they have exercised. Use one record per day, or - better - per exercise event (somebody might want to exercise twice a day after all!). You can create a (non-editable) Crosstab query for display purposes, but don't let that data display requirement drive you into an improper table design. John W. Vinson [MVP]
|
|
#4
December 24th, 2007, 10:50 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
Use one record per day, or - better - per exercise event (somebody might
want to exercise twice a day after all!). Are you kidding?!? 8^) Tom Lake -- My doctor told me I have to get in shape. I said, "Round is a shape, isn't it?"
|
|
#5
December 24th, 2007, 11:43 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
On Mon, 24 Dec 2007 17:50:59 -0500, "Tom Lake" wrote:
Use one record per day, or - better - per exercise event (somebody might want to exercise twice a day after all!). Are you kidding?!? 8^) Tom Lake Well, I admit that I get most of my exercise stretching points and jumping to conclusions! John W. Vinson [MVP]
|
|
#6
December 25th, 2007, 01:19 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
"Tom Lake" wrote:
Use one record per day, or - better - per exercise event (somebody might want to exercise twice a day after all!). Are you kidding?!? 8^) Sure one walk to the coffee shop, casino, bar for video lottery terminal or drink(s), corner store for smokes, liquor store and back. That's twice, right? Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
|
|
#7
December 27th, 2007, 05:33 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
How to normalize this table
Going with John's suggestion, I'd probably do something like:
tblExercise: ExerciseLogID PatientID DateEntered ExerTypeID (FK to tblExerTypes) Exer_Duration (long integer - minutes) Comment (for ExerTypeName = None) I like the idea of an Exercise types table because it allows you to add exercise types at a later time without having to add a column to your table structure. tblExerTypes: ExerTypeID (Long integer) ExerTypeName (walk, jog, run, swim, bike, None) ExerTypeSort (Integer - used to sort these values) If you need the WeekStart, you can get it for any date using the expression: WeekStart: [DateEntered] - Weekday([DateEntered]) + 1 HTH Dale -- Don''t forget to rate the post if it was helpful! email address is invalid Please reply to newsgroup only. "CoachBarkerOJPW" wrote: I have created asmall application in vb.net. Not relevent here I know , but the table structure of one of the tables is. Right now I have three tables, tblPatient, tblGlucose and tblExercise. I need to come up with a better solution for the exercise table. Right now I just update the table for everyday. Right now the records are kept based on the WeekBeginning field, so I want 7 records before I start a new row. The weekdays in the table are to give the user of the application a visual sense in the form of when they have exercised. Any suggestions? tblExercise ExerciseLogID PatientID WeekBeginning DateEntered ExerciseYes ExerciseNo MinutesExercised Sunday Monday Tuesday Wednesday Thursday Friday Saturday Walk Jog Run Swim Bicycle WhyNot WeeksTotal -- Thank you very much CoachBarkerOJPW
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
