Quote:
a new table database for every new academic year that will start but apparently, it's too complex.
No, you would just store the year as a filed within a table.
Quote:
The user will be asked to input their Student number name, contact details, and other basic information and also what school year the member had joined (example: 2016 - 2017) and it can store more than 1 of that data.
You can create a table called students that stores this information.
Then you might want a separate table to record attendance. Something very simple though. For example store the student_id and the year. That way the student table only has the 1 record per student but if you want to get a list of what years they attended you would join to the attendance table.