Sounds like something that could be implemented in a portal where each attempt is a record in the portal. But that's only a guess as there isn't enough info in your post to have a clear understanding of the design of your database.
There is an event table, an athlete table and a results table.
I have an event layout that has a portal showing results for that event from the results table. For the other field events I have added attempt 1, attempt2, attempt 3 fields to the records table but this won't work as there will be more than 3 attempts over the length of the event for each athlete. I am a bit reluctant to go a record for each attempt as this (as far as I can tell) will make it difficult to see the athletes and all of their attempts at all of the heights
I have attempted to add a screenshot of what it looks like in a spreadsheet
Where have you multiple fields within each result record, I'd use multiple records, all with the same event and athlete ID's. Then you can get as many results for a given athlete in a given event as you need. And either a single portal or a set of one row portals placed side by side to get columns of data can be used for recording the results for a given athlete or even all the athletes in a given event.
Thanks Phil - I am thinking that your suggestion makes more sense then what I was trying to do. I am thinking that having a set up such as
Athlete, Height, Attempt 1, Attempt 2, Attempt 3, cHeight Cleared (yes/no) would work. I am having difficulty working out how I would get the best height that an athlete has achieved though. Thanks for getting me over the first obstacle.
Max ( attempt 1 ; attempt 2 ; attempt 3 ) would return the greatest value of the three fields.
A summary field defined in the same table or a Max function evaluating from the context of the parent table can return the best overall height.