Jon,
From your last post in the Samples forum, you asked why the workout query didn't work.
First, don't name queries with the prefix "tbl". You might notice I use a fixed naming convention in my database objects. I didn't always do this, but have been "converted" by this site and a couple of others to start using good developer technique. Naming convention is part of good technique. You don't have to stay with my prefix convention, but you need to use something, and keep it consistant, or you'll end up getting REALLY screwed up.
Second, you're going to have to do separate queries for weights and cardio, they won't coexist. A union query might have given you a common record source for workout data, but the cardio data table has an extra field to record intensity of effort, and foils that.
You might work around that by having only one data table for cardio and weight raw data, and setup the 2 subforms in the main workout table by making 2 queries based on the same table, but that might not work. You'll have to decide that for yourself.
If you stick with the current table format, just make a query to run a progress report on a member's cardio workouts and a 2nd one to run a progress report on their weight workouts.
You really need to put more data into the current tables. I had a hard time seeing how it went until I put a lot more test data into the tables. More workouts AND more sets of exercises. More test data will let you see more in your queries and let you decide if everything is going like you want it to.
From your last post in the Samples forum, you asked why the workout query didn't work.
First, don't name queries with the prefix "tbl". You might notice I use a fixed naming convention in my database objects. I didn't always do this, but have been "converted" by this site and a couple of others to start using good developer technique. Naming convention is part of good technique. You don't have to stay with my prefix convention, but you need to use something, and keep it consistant, or you'll end up getting REALLY screwed up.
Second, you're going to have to do separate queries for weights and cardio, they won't coexist. A union query might have given you a common record source for workout data, but the cardio data table has an extra field to record intensity of effort, and foils that.
You might work around that by having only one data table for cardio and weight raw data, and setup the 2 subforms in the main workout table by making 2 queries based on the same table, but that might not work. You'll have to decide that for yourself.
If you stick with the current table format, just make a query to run a progress report on a member's cardio workouts and a 2nd one to run a progress report on their weight workouts.
You really need to put more data into the current tables. I had a hard time seeing how it went until I put a lot more test data into the tables. More workouts AND more sets of exercises. More test data will let you see more in your queries and let you decide if everything is going like you want it to.
