Create a Task List Plug in for Existing MS Access/VBA Application

In this MS Access/VBA project, you will build a task/reminder system that will be plugged in to a an operational Access database that has fifty users. When users logon to their database using the systems logon screen, their main menu will open up as usual (existing code). If they have any outstanding or recurring tasks in their queue, then your new task form will pop up in modal form above the main menu. They can review the list and click off checkboxes for any tasks they have completed, click OK, or cancel to resume their daily tasks. For example, Sally is a user who belongs to the billing department. Each month, a set of pre-assigned tasks pops up on the first of the month: a report for this, a report for that, some billing entries; perhaps a phonecall to a client who needs information each month. Sally makes the phonecall, checks off that item in the list, then clicks OK to close the form. She runs some reports, opens the task list from a button somewhere in the menu, checks off the reports and closes the form with the OK button. Features: - A user with admin privileges can set up one-time or recurring tasks for other users. - Other user roles can add tasks to their own list. - System can trigger itself on user logon to calculate which tasks should show in the list. - Tasks can be regular urgency or high-priority tasks. - You can design the tables (SQL Server/linked tables). - Tasks stay on the user's list until they check them off. - A task can be set to leave a task in another user's list when completed. ex. Sally finished a report, John gets task to review report. - A task can be set to call the existing SendMail VBA function to send an email to specified email address when completed. - A file/case number (max. 8 chars) can be specified on a task. - You will create a VBA sub/function that can be called from VBA to load a task into user's profile so that tasks can be hooked up to any other events in the system. Conventions: - Use LNC/hungarian naming conventions for objects and VBA. - Current design uses ODBC with DAO. Please use the same and not ADO. - Database format is .mdb, not .accdb. - Design to 32-bit Office/VBA. - Use the same colors and design feel of the current application. - You will provide a file with the new objects (queries, forms, reports) and a SQL query with the create statements for objects on the SQL Server side.