Thanks for all your help! I never thought about going the query route like that! It's 1:23am in Chicago right now, so I will be studying the code more closely after I take a rest 
You are right - I do have a button that says "Generate Schedule based off of Teacher Requests." My original intent was to have it be a two-step process. First, have the teacher locked teacher requests be added to the schedule. That would be the classes such as their lunch period (which obviously can't be first!) and their prep periods. So then tblMasterSchedule would populate with those records. Second, the button for dynamic requests (those classes that don't have restrictions for when they can be taught) would be clicked and those records would be added.
I wanted to get the portion of the code working that checked for duplicates before I worked on the part with the static classes. My original thought was to declare another varialbe for the yes/no field I have, and if the record for the class was "Locked", meaning the yes/no field was set to yes, I would have an If/Then statement around the code that basically says If Locked = False, then run code, Else do nothing.
I took that field off temporarily just to reduce complications, but it is something I am going to look at tomorrow. I want to study how this query that you came up with would affect my thought process.
You are right - I do have a button that says "Generate Schedule based off of Teacher Requests." My original intent was to have it be a two-step process. First, have the teacher locked teacher requests be added to the schedule. That would be the classes such as their lunch period (which obviously can't be first!) and their prep periods. So then tblMasterSchedule would populate with those records. Second, the button for dynamic requests (those classes that don't have restrictions for when they can be taught) would be clicked and those records would be added.
I wanted to get the portion of the code working that checked for duplicates before I worked on the part with the static classes. My original thought was to declare another varialbe for the yes/no field I have, and if the record for the class was "Locked", meaning the yes/no field was set to yes, I would have an If/Then statement around the code that basically says If Locked = False, then run code, Else do nothing.
I took that field off temporarily just to reduce complications, but it is something I am going to look at tomorrow. I want to study how this query that you came up with would affect my thought process.
