Hierarchical db - need no-edit option in form

[E.Q.]

Greetings -
I have a database that includes a skill set definition part that is strictly
hierarchical in design. The other part of the database tracks employee
training.
The hierarchy(from top to bottom) goes Work Group, Skill Set, Skill,
Measure, and question with a structure that looks like
tbl work group:
lngWorkGroupID - PK
chrWorkGroup

tblSkillset
lngSkillSetID - pK
lngWorkGroupID -fk
chrSkillSetName
chrSkillSetDescription
etc.

tblSkill
lngSkillID - pk
lng skillsetID - fk
etc

tblMeasure
lngMeasureID - pk
lngSkillID - fk
etc

tblQuestion
lngQuestionID - pk
lngMeasureID - fk
etc

I created a skill set using these tables by having a form with three nested
subforms (frmSkillSet, s_frmSkill,s_frmMeasure, s_frmQuestion). I have that
on my front end and designed a front end so employees could track training
and print out skill set reports, but not define the skill set information in
the database.

Another work group would like to use a similar database. I created a copy
and deleted the info for my work group then sat with their supervisors. We
developed the skill set down to the "Measure" level; but they would like to
have their employees write the questions.

We agreed that it would be best to have a "no edit" form to do this, but
when I try to apply "no edit" to the nested form I have, the sub forms
disappear.

I thought perhaps a set of "no-edit" definition forms (one for each level)
would work, but I'm having trouble getting the Question level to work (I
haven't tried the others).

So I would like a form where the employee writing the questions works his
way down the hierarchy by selecting the skill set, then the skill, then the
measure to enter training questions. I don't know if my existing nested form
can be used or if I need to build a set of new forms.

Thanks in advance
EQC

 

[E.Q.]

That looks to work perfectly!
I played around with making some cbo's null and turning enable on and off to
get it to act the way I think it should with each after update events, but
the basic structure you described was right on.
I hope to show it to the users soon and see what they think.
Thank you very much.