Design a Microsoft Access Database for Multiple Project Task Lists
Question details
The user wants to store multiple project task lists in a single Microsoft Access database.

- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- A new Access user wants to organize project task lists in one database, similar to using multiple worksheets in Excel.
- Observed behavior
- The goal is to view and manage each project's tasks while storing the data in related tables.
List the project and task details you need to track, such as names, due dates, and status. Decide whether the same task record can belong to more than one project; this determines which relationship to use.
Create Projects and Tasks tables with a one-to-many relationship
Use this structure when each task belongs to only one project, even if different projects have similarly named tasks.
Access stores related records in tables rather than separate worksheets. One Projects table and one Tasks table can hold all project lists, with ProjectID linking each task to its project.
In Access, choose Create > Table Design. Add ProjectID as an AutoNumber primary key and add fields such as ProjectName. Save the table as Projects.
Choose Create > Table Design again. Add TaskID as an AutoNumber primary key, ProjectID as a Number field with the Long Integer field size, and fields such as TaskName, DueDate, and Status. Save the table as Tasks.
Open Database Tools > Relationships and add Projects and Tasks. Drag Projects.ProjectID to Tasks.ProjectID, select Enforce Referential Integrity, and click Create.
Open the Projects and Tasks tables to enter records, using the matching ProjectID for each task. To view one project's list, create a query and set a criterion on ProjectID, or use the Form Wizard to build a project form with a task subform.

Add a junction table for tasks shared by multiple projects
Use a junction table when the same task record can belong to more than one project.
Track project task lists in WPS Spreadsheets
For a spreadsheet-based approach, use WPS Office as a free, lightweight alternative with a familiar interface. Open an existing workbook or organize project tasks in sheets as you migrate from Excel. WPS Spreadsheets does not create or replace an Access relational database.

Frequently Asked Questions
Do I need a separate Tasks table for every project?
No. Store all tasks in one Tasks table and link them to Projects by ProjectID. Use a query or a project form with a task subform to display one project's list.
When should I use a junction table?
Use a junction table when one task record can belong to multiple projects. Create a ProjectTasks table with ProjectID and TaskID, then link it to both main tables in Database Tools > Relationships.
Where should I store a task's due date and status?
In a one-to-many design, add DueDate and Status to the Tasks table. If a shared task has a different due date or status for each project, add those fields to the ProjectTasks junction table instead.
How can I prevent a task from referring to a nonexistent project?
In Database Tools > Relationships, link the relevant ProjectID fields and select Enforce Referential Integrity when creating the relationship.




