Maybe your right. But your suggesting me of thing that i don't understand yet and i don't have enough time to study and go back to design. How bout i populate all the time(from 7:00 am - 5:00 pm) then when user update the system will prompt if the given day and time has a conflict.
Coming up with a good design doesn't take as much time as you imagine. And it's the most important skill you can have as a programmer. And it's much more important than "coming up with something" on this particular assignment in this particular class. Better to fail on an assignment than to fail in your career. You can ask anyone who has achieved success at anything and they will (without exception) tell you that what I'm saying is true. In your heart, you already know it's true.
You need to look at each element of the data you want the user to input and ask yourself, "What am I expecting the user to input?" and "What other things might the user input that will create problems?" and then "How can I change my design to eliminate the problems?".
Then, when you go to write the code, you will find that there are a lot of conditions that you don't have to write code to check for because you will have designed the possibility of those conditions out of the software. Your code will be simpler, easier to write and debug and easier for someone else to read.
Hoppy