Clarity,
I just assumed you were already finished because the layout actually looked good. If you haven't set up the tables yet, I would be glad to help you out in any way.
You mentioned table and field naming conventions...I would always recommend naming everything so that it is easy to identify and use in your applications or in reports. If you get too technical in the names, the data becomes very hard to put together or to design around.
I really like the theoretical structure that you have set up. I would recommend taking fields that have the potential unlimited rows (such as kids, because players can have multiple kids) and set them up in an alternate table. This table would be small and not contain much information...but it will cause a lot less administrative headache than having Kid1, Kid2, Kid3 all the way up to 12 (if they are amish). There may be other fields like that as well, but I didn't notice them right off hand.
If your table needs relationships set up, I wouldn't mind mapping a visual representation of the data you've shown. From that, we could set up the primary and foreign keys to make the relationships between tables.
You may have all this done, I guess what I'm saying is...I don't mind helping with anything that has yet to be finished. But as far as concept...I think the database is set up pretty efficiently.
On another totally seperate note...
What software is used to run this site? I was thinking of looking into it for another page.
