Making an input in one table the field in another.

[bflemi3]

I am tracking contract requirements. One requirement could be acquisition. There are sub requirements under acquisition. Not sure what the best way to do this is, but I think I should input data into one table (e.g.: the acquisition category) and that automatically creates a new field in another table (acquisition sub category). Is this possible to do?

Thanks for your help in advance.
...Still learning

 

[Norie]

It is theoretically possible but I certainly wouldn't advise it.

What I wpuld do would create a contract requirements table.

It would have 2 fields - one a unique identifier for a contract (this would be taken from the main contract table, asssuming you have such a field.

The other field would contain the requirement.

With this set up a contract can have from 0 to many requirements.

 

[bflemi3]

I'm sorry I don't quite follow you. Could you give me an example please.

Thanks for your help

 

[Norie]

What don't you understand?

 

[bflemi3]

I understand the part about setting up a contract requirements table. But There are sub requirements (eg: Under Acquisition would be Acquisition Life Cycle Documentation, Acq. reporting, and Budgeting and Cost Estimating). What table would these be stored on.

My main goal is to create a form that has a combo box. You select the main category of contract requirements, then in a subform or a list, base off of what main category you chose, you would be able to select multiple sub requirements. Does that make sense? and if so, is it possible?

Thanks

 

[Norie]

I think I know what you are trying to do and it is possible but why not just store the sub category in the requirements table?

 

[bflemi3]

This is what you are saying?

CtrctReq subcat1 subcat2
Acquisition Acq. Reporting Budgeting & cost estimating

This what I am saying:

Acquisition Risk Mngment Program Mangmnt
Acq. Reporting Risk Assesment Prjct Plan & Control
Budg. & cost est Risk Mitigation Prjct Reporting

There are more than just two subs per Main, but this is just an example. There could be as many as 20 or 25...it's hard to say.

 

[Norie]

That isn't what I'm saying.

I'm saying just have one field for CtrctReq

CtrctReq
Acquisition Reporting
Acquisition Budgeting & Cost Estimating

 

[bflemi3]

That didn't come out right

you are saying:

CntrctReq Subcat1 Subcat2..... SubcatN
Acquisition Acq. Reporting budgeting & reproting
Program Mngmt prjct plan & cntrl project reporting


I am saying:

Acquisition Program Mangment XXXX YYYYY
Acq. Reporting Pjct plan & contrl dfd fgsdfg
budgting & report projct reporting fgf dhfas

Thats what I meant...sorry

 

[Norie]

I'm saying don't have a field for subcategory at all.

Just have a field for the requirement and include the subcategory.

CntrctReq
Acquisition Reporting
Acquisition Budgeting
Program Mngmt Plan
Program Mngmt Reporting