Database deisgn
I have been given a task to create a small database to keep track of the activities of our small group in which the members give contrinutions per month and borrow money. One table I'm sure I need is 'Members' which shall have details of the members. When it comes to recording the transaction for each member each month, having the members table with enough fields to record the transaction month by month sounds so inneficient and against the spirit of good design. This would also mean I need to add new fields every month to enter transactions for each member. This is the kind of info I will keep for each member:
AmountpaidJan2004
AmountborrowedJan2004
TotalAmountSavedAsAtJan2004
AmountpaidFeb2004
AmountborrowedFeb2004
....
....
. all these as fields to take data for each member.
Without actually solving the whole problem for me,could someone kindly give me hints or post similar sample databases?
I have been given a task to create a small database to keep track of the activities of our small group in which the members give contrinutions per month and borrow money. One table I'm sure I need is 'Members' which shall have details of the members. When it comes to recording the transaction for each member each month, having the members table with enough fields to record the transaction month by month sounds so inneficient and against the spirit of good design. This would also mean I need to add new fields every month to enter transactions for each member. This is the kind of info I will keep for each member:
AmountpaidJan2004
AmountborrowedJan2004
TotalAmountSavedAsAtJan2004
AmountpaidFeb2004
AmountborrowedFeb2004
....
....
. all these as fields to take data for each member.
Without actually solving the whole problem for me,could someone kindly give me hints or post similar sample databases?