Junction Table Form Design

[mahoney.jonathan]

I'm currently working on our project database. What we want to do is
for each project, track what tasks need to be done, their complexity
and from that estimate duration for each developer type.

I have setup currently:

tblComplexity
complexID (autonumber)
complexName (with the following values)
Low
Med
High

tblTask
taskID (autonumber)
taskName (with the following values)
GUIDesign
MDBFeed
Report

tblCostLookup
costLookupID (autonumber)
complexID (lookup from tblComplexity)
taskID (lookup from tblTask)
BADuration
SADuration
SEDuration

So tblCostLookup is completely filled in, each task has a value for BA,
SA and SEDuration for each task/complexity combination.

I have a built a query that can read the values and calculate each
duration which is easy. I can get that to appear in a form using a
subform bound to the query, which just reads the fields from the combo
boxes on the main form.

The problem I'm running into is each project can have multiple tasks,
so I need a contin. form setup which I tried using a subform,
unfortunately you can't have a subform in a contin. form.

Any help would be appreciated this is really hanging me up at the
moment.

 

[Larry Daugherty]

Yes, you can. That's the way I normally use them.

Assuming that your main form is bound to the Project, design your Task
subform as short as possible so that at the bottom of your main form
you have plenty of room for a subform control that will show multiple
instances of your subform. Make the subform's default view
"continuous forms". The query for the subform should have ProjiectID
in it, usually as the first field. When you have your Form and
subform working together the value of Link Master Field and Link Child
Field should equal the same thing, almost always the same name.

HTH

 

[mahoney.jonathan]

Larry thanks, I'll give that a shot this afternoon.

Dorian,

No I don't want to reinvent the wheel, but unfortunately I'm going to
have to for the time being. We're in the process of evaluating in
having companies come in and demo PPM tools for our organization.
Unfortunately, like many companies, it's a very very slow process and
we have immediate needs. We're not looking at having a PPM tool up and
running for another 12-18 months. I already had the database up and
running and tracking time and status reports etc. but we do need some
additional functionality.

Thanks,
Jonathan