Data Base

Data Base Order Description Assignment Instructions Instructions: You will create a database base on the followin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing scenario. Scenario: Joseph L’Dey is organizational challenged. He is very talented and when he gets around to doin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing anythin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing he generally does it very well. The problem is that he just cannot keep up with what it is he needs to do next. He has decided that he needs to take the database skills he learned in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in class and build himself a tool that he can use to organize his life. Unfortunately, Joseph has forgotten to get it built, so he needs your help. What is needed is a database table that Joseph can use to keep up with the tasks that he needs to do and when they need to get done. In a moment of organizational in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">inspiration, he did manage to make a list of the fields that are needed in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in this table. These are shown in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the table below. Field name Data Type Description taskDesc Text A description of the task that needs to be done. taskPriority Number (in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">integer) How important the task is relative to others in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the database. Stored as a number from 1 to 5 with 1 bein" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing the most important. taskDueDate Date/Time The date when the task needs to be completed. For some items there may be no due date. taskCompleted Yes/No Whether or not the task has been completed taskCategory Text The number of shares in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the block of stock. Your Task: Build a database with the table described in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the Scenario. Create a form that Joseph can use to enter tasks. Add queries to the database that will help Joseph by answerin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing the followin" rel="nofollow">in" rel="nofollow">in" rel="nofollow">ing questions. What items are due within" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in the next week? (Save this query as weeklyTasks.) What tasks are stored for the “school” category? (Save this query as schoolTasks.) Are there any tasks with a priority of 1 that are due today? (Save this query as highToday.) How many tasks for the “Work” category have been completed? (Save this as workDone.) How many tasks from last week were completed? (Save this as lastCompleted.) Which tasks are stored that has no due date or a priority of 5? (Save this as lowTasks.) Also, create a report based on one of the queries that will show the tasks for the next week in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">in order of due date and priority. You should make up data and enter it in" rel="nofollow">in" rel="nofollow">in" rel="nofollow">into your table to test the components that you create. \