First the caveats. I didn't read your requirement documents and don't think most people on here will. This board is filled with people who actually use Access in the real world. I've found there can be a disconnect in what teachers want and what the best actual method is for laying out a database. So any suggestions you get here, be sure to make sure they jive with the instructions you receive. The instructions you receive here may not be the text book answer your instructor expects, but would be the ones I suggest you employ if working in the real world.
So, with my real world eye, this is what I see with your databases:
Database A - I'm picking nits with this one-overall it looks very good
tblInstructor - #1. I think fldEmail needs to be a text field, not a hyperlink. An email hyperlink must take this form: 'mailto:yourname@thissite.com'. The 'mailto:' needs to be part of the hyperlink and when you do that, you rely on everybody who edits your hyperlink data to make sure that part is included. #2. You might need an autonumber primary key instead of the Short Text one you have. My guess is fldInstructorID is assigned outside this database so you need to use that. How does fldInstructorID get assigned?
tblClasses - what values go into fldprerequisite? Is it other classes? If so, you would make this a numeric field and feed in other records fldClassID values. If not explain. Also, could a class have multiple prerequisites?
Database B - You have 4 tables in this database, but I only see a relationship that includes 2 of them (tblDepartments & tblExpenses). tblTraining and tblEmployees aren't related to any other tables.
tblDepartments - I think you reversed your fields. fldDepartment name is a number and fldDepatmentID is Short Text.
tlbEXpenses - #1. fldAmountExpend is a Short Text field, but the word 'Amount' in it name makes it sound like it should be a number. #2. fldDepartmentID is ShortText, but it probably be a number.
tblTrainingID - this only has an autonumber field--it serves no purpose without other fields.
My last note would be to use the Description field on all your tables. In design view, where you assign field names and datatypes, theres a 3rd field--Description. Use it. Tell me what the purpose of each field is for. I don't know if your teacher cares, but you get extra credit in the world for that.
