windows user id

[Douglas J. Steele]

Sounds like you've got a many-to-many relationship between Projects and
Tasks (each project has many tasks associated with it, each task can apply
to many projects). That means you need three tables: one to hold the details
about each Project, one to hold the details for each Task, and an
intersection entity to hold the details about specific tasks for a given
project. You'd store the Id of the user in that third intersection entity.

 

[Erin Freeman]

Hi Douglas,

I have one table filled with project specifics, each project gets a
checklist, so i have one checklist table, what would the 3rd table look like?

 

[Douglas J. Steele]

Assuming that you've got ProjectId as the primary key of the Projects table,
and TaskId as the primary key of the Tasks table, the primary key of the
intersection entity would be the combination of ProjectId and TaskId. You'd
also include the user id as a field in that table, as well, possibly, as a
date field.