Separate tables for each week? No, no, no. You just need one "performance" or "event" table, with date and event info, and an athlete ID field that you link to the athlete ID in the person table.
You can show the athlete's events info in a portal, on a layout based on the person table.
To see performances of all athletes on a given day, you'd search for that day in a list layout based on the event table.
Does that make sense?
Thanks Tom - thats has helped me immensely! i have realised that i needed to adjust the fields that i would use.
If i can be so bold as to ask another question? I have two tables. 1 = fixtures, 2 = match statistics. these are linked through a relationship. is there a way that i can have opposition as a drop down menu in a field in the stats table and that by selecting an opponent it autofills other data fields such as date, ground from the fixtures table into the relevant fields in the stats table?
Disregard last post - i have found the solution using a lookup. Thanks again for your help