Sounds like you need to re-think your design.
A) you don't need different layouts
B) you should set up your records so that each person's data is put in a different record each day
You can then use an expiration date in the record as well as the person's account name to control which records can be edited.
Not sure what you mean. Right now I have a 6-week challenge and I have each person having Week1 fields = W1S, W1M, W1T, W1W, W1TH, W1F, W1SA, Week2 fields = W2S, W2M, W2T, W2W, W2TH, W2F, W2SA and so on for each of the 6 weeks. So each person's record consists of 42 input fields and many calculated fields.
To apply that to your specific set up, you'd set up fields like this:
as many data fields as needed to record participant activity here (steps walked, etc.)
That results in 42 records for each person. Each one tagged by the person's ID and the date. One record per person per date.
This can make for much simpler reporting and analysis at the expense of a somewhat more complex design for your data entry screen.
Thanks that helps as I was thinking to expand the challenge to include biking, swimming, etc. next time.
I'll have to think about how this all fits in with the teams and the team statistics that I show each week. I average the total minutes per team by the active members of the team as I have 16 teams consisting of 3 members up to 59 members. I show those statistics per day with the week total. It was interesting how it affected participant minutes when we got clobbered by a snow storm the other week.
It's a matter of setting up the right tables and relationships. You can set up a table of teams, a table of participants, a table of activities and a table of activity measurements (assuming that the data collected for each activity is sufficiently similar that the same or nearly the same type of data is recorded for each.)
Teams-----<Participants----<ActivityMeasurements>-----Activities (---< means "one to many" )
Teams::__pkTeamID = Participants::_fkTeamID
Participants::__pkParticipantID = ActivityMeasurements::_fkParticipantID
Activities::__pkActivityID = ActivityMeasurements::_fkActivityID
Summary reports, cross tab reports and charts can all be generated from the data in ActivityMeasurements with data pulled as needed from the other tables to show team, participant and activity names.
Note that none of these tables should be linked by a name, but rather by an internally generated ID such as a serial number or Get ( UUID ).