Okay, made some changes to your db--see if they make sense.
Here's a short list of what I did:
1) Look at the tables with NEW in their name--they're modified--not perfect, but better I think. Of greatest note, the courses table's fields are almost all changed to number data types since they all reference other fields.
2) Look at the relationships (Tools->Relationships).
3) When you open the courses table (not the form), notice how it appears that there is text in each record. However, these are really all numbers. If you look at the design, you'll notice under the Lookup tab of each field is SQL referencing the table and the fact that I made the column width of the column holding the primary key, an autonumber, to 0. Therefore, the user doesn't see the number since it's meaningless to the user.
4) I'm not sure if course and student ID's are manufactured by you, or if it matters what they are. I went with the assumption that you may need to assign a specific ID to each. However, I still added a primary key to each table since I like that approach to relating tables. There is another field where you can enter a text ID if needed for each.
5) On the courses form that I generated with a wizard real quick (so, needs a lot of clean up/formatting) you'll notice that you have combo boxes for each item. The SQL for each one was automatically generated by the wizard since I set it up that way in the table design. Likewise, the labels all had good names since I gave a caption to each field. You may also note for the student name how the last and first names are concatenated into one field for that combo box.
The key is to remember that inside Access it's really storing all the related fields into the courses table with a number--but, you really never see it unless you want to.
Obviously, what I've given you isn't done by any means, but I hope it makes sense. Also, as a side note, you have established a number of one-to-many relationships. For example, one disability may be associated with one course. However, is it ever possible that there may be multiple disabilities associated with a single course (or any of the other fields)--in that case, you may need to set up a many-to-many relationship.
So, to recap--not perfect and not complete, but I hope the attached DB helps!