Guidance on Normalisation

[Negger]

Hi, I'm currently constructing a DB which should have <1000 records when completed. I'm aware of the Normalisation issues, but uncertain as to how far to take it ? As an example, I have 14 clubs under the one league. Should I create a separate Club_Table, or can I simply use a 2 Column Combo (ClubName, ClubID) with the ClubID being Bound, and select for each new member ?
Ditto with Fields such as Club Officers e.g. Capatain, Vice Captain, Secretary, Treasurer etc, a max of 10-15 choices, should this be a separate Officers_Table ?
I can see that I could easily end up with 10+ Tables, each with only 10-15 entries in each ?
Should I be going that way, or can I stick with Combo Box selections ?
Any useful "rules of thumb" to follow ?
Regards

 

[jdraw]

Perhaps you should post your data model and some sample test data. I wouldn't be concerned with combo boxes at this time. I think the bigger issue is to tell us what the data base is about, what is it for???

You may get some ideas here
http://www.databasedev.co.uk/football_soccer_data_model.html

 

[Negger]

Thank you both for your input. With regard to what it is for; It originated as a simple tool to aid administration of a "team", this has now rapidly expanded to do the same for a "League" & I suspect "mission creep" will set in and financial data may well end up being included.
As even 10 items in an Expression are fiddly, I think I will create at least a separate tblClub as there is other Club specific info that could be held in it i.e. more fields could be added.
Coming back to my original point, can I take it that there is no particular downside to having many small tables (containing different data types) rather than trying to hold everything in a single large one ?
Regards

 

[Negger]

Dear Pat, Yes I did read your first post, but I'm guessing that the significance of what you've written has escaped me ?, and the " - a table of tables and a table of table items" has completely lost me ?
Regarding your second post, I really don't expect several of these potential new tables to change much at all over, say, 10yrs, perhaps one addition/deletion, so maintenance shouldn't be a problem- and I think you've answered my question "create as many tables as you want". So thank you again.
Regards

 

[jdraw]

I think you should do a little research on Normalization. That will help you in determining what tables you need, and how they relate to each other.
The data model link in my last post was meant to give an idea of what others have done, and may be applicable in part to your project.
The first few topics at this site should give you guidance on table design

http://www.rogersaccesslibrary.com/forum/topic238.html