You may find it simpler to bring the Present_Level table into the same file as Student_Info. This makes for simpler relationships and any scripting that moves from one table's data to the other will be simpler as well. Managing password access is also simpler as you have just one file to which to set up password access instead of two.
I suspect that you use a separate file so that you can start over with an empty file each year. If so, there are alternative designs that do not require such separate files for the same data from different years.
Working from your current design....
In which file are you when you work with the Present_Level data? You can add layouts to your Student Info table that refer to Present_Level or you can use Layouts created in the Present_Level file. Which do you have?
Your relationship also appears backwards in this screen shot. It shows a Many to one relationship, many students to one Present_Level record instead of a one to many or one to oen relationship. This suggests taht Student_Info::Student_ID is not defined as an auto-entered serial number as it should be.