Creating Action Items with several one-to-manies - need design advice

[christine@milton]

How should I design the tables/queries?

I have an action item list that I want to put into access but it isn't always
one line per action item, not sure how to set it up, below is an example:


Action Item 1:
Building Improvements

Action Item 2:
Paint the building

Action Item 3:
Choose color Duration: month Cost: none
Leader: John
Hire contractor Duration: month Cost: none
Leader: John

And the next record could be like:

Action Item 1:
Implement Sales Strategy

Action Item 2:
Decide strategy Duration: month Cost: 1000
Leader: John
etc,

Action Item 3
empty

______________
Duration, cost, leader can be under lvls 1, 2 or 3

Please advise,

Thanks!

 

[mnature]

Always design tables first. Don't worry about queries until you have set up
your tables, and normalized them.

It sounds as if you need a table to list projects, and another table that
will list the actions to accomplish those projects.

The project table will have a primary key, probably an autonumber, that will
uniquely identify the project. The Action table will have a primary key
(autonumber), that will uniquely identify the actions. The Action table will
also include a field that will link back to the project table (use
relationships), and identify which action goes with which project. You will
set up various fields in each table. The Project table will probably include
leader and text fields, the Action table will probably include duration and
cost fields. You may want to include a Finish Date in the Action table.

Once you have set up these tables, then you can design queries and forms
that will allow you to input data, and reports so that you can print out what
is happening.