Thanks for the response, Tom. One reason why I split the WorkoutMethod into their own table is so I can use those values in a drop-down menu in the application. I'd rather have them available as choices rather than enter them free-form into a textbox lest things get too messy in record-keeping. I figured that this was the best way to do it.

Do you agree with this, or is there a better way to do it?

I might also have friends keep track of their performance through my application as well, so keeping it as tidy as possible is probably the best way to go. I did move the fields from the WorkoutMetrics table into the WorkoutSession table, though. Again, any final recommendations which you can make would be appreciated. I work with data all day long but rarely, if ever, do I ever get to design a database so this is very helpful.

Thanks!!