I'm just curious if it makes sense to use junction tables in this instance:

student - studentID, studentfirst, studentlast, gender, age (adult, teen, or
child), lessonday, status (current or retired)

address - addressID, address, city, province, postalcode

phone- phoneid, phonenum, extension, phlocation

email - emailid email, emailLocation

gaurdian – gaurdianid, gaurdianfirst, gaurdianlast, relationship


studentaddress - studentID, addressID
studentguardian - studentID, guardianID
GuardianAddress - guardianID, addressid
Studentphone - studentID, PhoneID
Guardianphone - guardianID, PhoneID

Notes on this table:
I'm a music teacher who teaches an average of 50 students at a time. I'm
trying to build a database track contact info, invoice students, and track
attendance. I'm starting off with the contact portion of the database and
once that is done I'll move on to the rest.

-Adult students don't have guardians
-Students with divorced parents may have 2 addresses and 4 Guardians. Not
many students in this situation
-Most parents have 2 emails and phone numbers
-Some young students may provide their own phone and email

That's it, thanks in advance