hi
@Fandy ,
adding on ...
I would make a field in each table with an AutoNumber field to be the primary key. I like to put ID on the ends of these fields (StudentID, PaymentID, FeeID), which means you need to call the student number something else ... if it's text, maybe StudentCode? Best not to use spaces in field names.
The Fee table needs StudentID Long Integer (Default Value is Null) to correlate it to the student
You should have a FeeTypes table with AutoNumber FeeTypeID and a text field, FeeType, to describe it. The Fee table would then also have a FeeTypeID Long Integer (Default Value is Null) with different records for each fee, instead of using different fields -- this is a common mistake. Then all the fees are in the same FeeAmount field, and you can always get a total for each student
The Payment table needs StudentID Long Integer (Default Value is Null) to correlate it to the student
This structure allows them to make multiple payments. You can use a query or form to add fees and payments up to get a balance.
This is pretty simplistic, but a good start ... by next year, you'll be better with Access