Over 500 Tasks; Yes/No in project?

[Parts Manager]

Hello,

I have a table that has over 500 records and those records have a 'taskId'
as the primary key. Each of the records relate to what the task is that can
be done in a project.

What I am looking to accomplish now is have a form where all 500+ tasks show
up with a Yes/No type of check box. The default would be that all tasks
would be checked with a yes. Then the project manager can go through the
list and click off/NO to those tasks that are not needed on this project.

Each project has it's own ID also as the primary key.

I am trying to find out what is the best way to handle this. The table of
projects is set, the table of tasks is set; but I am not sure what would be
the proper way of utilizing a large checklist like I am thinking of. OR, if
there is another way instead of Yes/No and rather a method where just adding
a field in the TASK table to include a yes/no and have the Project list pull
that data out.

Any suggestions or procedure on how to make a table (or use the existing
Task table and Project table) where I can have a form that an end user can
pick and choose what tasks are to be in this project?

My concern is that I don't duplicate data already available in tables and
find a way to make this list of tasks per project. We plan to list all
tasks and then click yes/no in the list; then print out the list so we have
a master plan for the project of what tasks are in this project.

Tim

 

[John Vinson]

Any suggestions or procedure on how to make a table (or use the existing
Task table and Project table) where I can have a form that an end user can
pick and choose what tasks are to be in this project?

As with any many (projects) to many (tasks) relationship, the proper
technique is to add a third resolver table: ProjectTasks, with fields
for the ProjectID and the TaskID. Do you REALLY want to default to
having all 500 tasks selected for each and every project? Is there
not some subset of "must do" tasks which apply to every project, and
other tasks that depend on the nature of the project?

John W. Vinson[MVP]

 

[Parts Manager]

As with any many (projects) to many (tasks) relationship, the proper
technique is to add a third resolver table: ProjectTasks, with fields
for the ProjectID and the TaskID. Do you REALLY want to default to
having all 500 tasks selected for each and every project? Is there
not some subset of "must do" tasks which apply to every project, and
other tasks that depend on the nature of the project?

John,

You are correct, I don't really need to make all 500+ tasks defaulted to
Yes; but a subset of about 400 are 'must do' tasks per project.

Task table as over 500+ task items; the Project table only has the ProjId,
BoatId, TaskId, and a Yes/No field at this time. My thought was that I
would create a new project with ProjId; and pull the boat from the BoatId,
and then I will need to bring in the Task(s) needed on this project. And
there in lies why I have a ProjList Yes/No field. But this is where I am
confused on something that seems simple. Each Project would have many
Tasks.

In laymans terms;

Project: 01
Boat: SG-65
Task: A-101
ProjList: Yes

Project: 01
Boat: SG-65
Task: A-102
ProjList: No

etc.....

Then I thought I would then be able to use the Project table to print out
all the tasks that are Yes to Project 01. However, The way I describe
above, it would seem that I would have to enter (choose from listbox) each
and every task that is needed; which is not what I had intended. Since
there are 500+ tasks, maybe my ProjList Yes/No field should be in a
different table or I am not seeing the view correctly. Hell, maybe this is
normal.

Am on the right path or have I stumbled in this area?

Tim

PS: As I look at the tables, the Project table is pulling from BoatId in the
boat table and TaskId from the task table; maybe a project table is not
needed since a project is really a boat. This leads me to think that I
should move the ProjList Yes/No field to the Boat table.....but I am still
confused.

I have been doing well up to this point, but I can't figure it out in my
head how to handle the relationship of a boat having many tasks, but not all
tasks, and really a project is a boat so maybe I shouldn't even have a
project table. I think what I did is imagined that I had a questionaire
with 500 questions on it and would have an answer table with the answers.
So this would give me a Task table (questions) and a Project table (the
answers).

I just re-read your reply to me. I have boats and tasks in a third resolver
table of Projects, so maybe I already have it right?

Confused for thinking too much about this one section.......