Design Help
Design Help
(OP)
Hello there, I am fairly new to the database world and quite enjoy the programs available. I too am not as saavy at database stuff, but rather spreadsheet stuff. I think it is time to switch to databases.
OK, my design question; what I have is a spreadsheet that looks after approximately 150 bowlers. Every year, each of us bowl in 3 manditory tournaments and one voluntary tournament. The bowlers are from 6 separate zones as we call them, but represent one province (Canadian eh!). Each year, we are allowed to drop one tournament from the 3; lowest one normally. So your season total is based only on two of the three...With me so far? What I need or would like to do is replicate this in a database program (Access / Filemaker). The reason is that, I now have been asked to store every tournament they bowl and number of game in each for a lifetime average. I think i know the tables I need, but I am not sure. I think a need a self relating table for the tournments for the lifetime average.
Anyways, if you have any ideas or questions, please let me know. This is important to me and to our zones.
Mikajake
OK, my design question; what I have is a spreadsheet that looks after approximately 150 bowlers. Every year, each of us bowl in 3 manditory tournaments and one voluntary tournament. The bowlers are from 6 separate zones as we call them, but represent one province (Canadian eh!). Each year, we are allowed to drop one tournament from the 3; lowest one normally. So your season total is based only on two of the three...With me so far? What I need or would like to do is replicate this in a database program (Access / Filemaker). The reason is that, I now have been asked to store every tournament they bowl and number of game in each for a lifetime average. I think i know the tables I need, but I am not sure. I think a need a self relating table for the tournments for the lifetime average.
Anyways, if you have any ideas or questions, please let me know. This is important to me and to our zones.
Mikajake
Talk To Other Members
RE: Design Help
Those entities will be your tables.
Within your tables, define every single information related to the given entity (details), those are your attributes, and in FM your fields.
When this is all ok, start tothink about making combinations and relationships to have the outcome you want.
Post back when you are ready with those basics.
It's too hard to give you an answer based nearly nothing or at least not real data in a table.
While building your tables and fields you will 'see' which information you need for the desired outcome.