Hey Heather,
First off, thanks for the quick reply!
The way I have it setup right now isn't all too complicated... there is a classes table to store information about the specific classes (including the teacher's ID number), then on the users table, each student has a class ID that they're associated with. So all of that doesn't seem too bad, really... Well, for right now, at least. I don't think I'm too worried yet with how the MySQL queries will work out until I can visualize how students and teachers will view the given pages. I think I'm okay with the secondary page (teachers will be able to sort by columns to view all work by one student, all work by one class, etc), but I'm not sure how it should work in an easy way that will allow teachers to control which language each class is on, and the teacher's list of words for that language, without it being too confusing. I'm worried that if I make the teacher select one class or the other at the beginning, that they will do something for one class then forget about the other (or accidentally lose information), and if I put it all together on one page, that it'd be too overwhelming.
What are your thoughts on organizing the front end, first? Then, with that settled, we'll come back to the MySQL query and how that should work out, later.
I hope that's okay with you. Thanks again for the help!
-Ange52