Am I Using Too Many Fields?

[mginipro]

I'm designing a database in order to track the ratings of certain skills in four different zones on a volleyball court and across six rotations. Now, I've got my six rotation layouts done with buttons and the fields for the four zones.

An explanation of what I'd like to record is whether a players contact on a ball is rated as a 3, 2, 1, or 0 within a specific zone in that specific rotation. I'd then do that on every serve and for every rotation.

I know that I can get this done by just creating separate fields for every zone, every rotation and every rating, then creating calculation fields that just do the averaging math for me.

Ex. Rot1Zone13Pass, Rot1Zone12Pass, Rot1Zone11Pass, Rot1Zone1Ace, Rot2Zone13Pass, Rot2Zone22Pass, etc.

It's just going to be a ton of fields and I was wondering if there was a way to do this within a calculation. What I want at the end is the average passing rating per zone per rotation. I don't mind creating all the fields I need, but I figure there is probably a calculation that could make this simpler to design. I just don't have the experience with calcs and scripts to think of it.

Thanks!

[comment]

I believe you should have one field for the zone, one for the rotation, and one for the rating (and I guess one for the PlayerID?) - and a separate record for each rating. Then produce a summary report.

[bruceR]

Agreed. Not mentioned so far is some kind of bigger picture consideration as well - probably need a playerID and gameID?

Edited June 4, 2010 by Guest