child of a child of a child on a form.

[wdsnews]

We want to record the teaching licenses of our teachers. I'm looking for an
efficient screen space solution to display multiple child tables/fields.
The good news is we only need to display one field from each record. But
the one-to-many relationships mean there are multiple records to display.

o Each Teacher can hold multiple licenses.
o Each License can carry multiple endorsements, such as Art and Math.
o Each Endorsement can carry multiple Authorizations, such as HS or ML.
(For example, a teacher might be able to teach Art to high school students,
and Math to both High School and Middle School students.)
o Authorizations are short, no more than 8 characters.

Here's the picture I have in my mind. I want each Authorization listed side
by side to the right of each Endorsement. That arrangement would allow
Endorsements to be listed in a normal columnar view, one below the previous.
I could use the normal navigation buttons to advance from one License to the
next, allowing the user to view all the Endorsements and Authorizations for
each license.

Can that be done? How do you list child records side by side? Is there a
different efficient arrangement?

Four tables are linked one to the next in a one to many connection;
Teacher -> License -> Endorsement -> Authorization. Most tables have only
three fields; ID (index), Displayed Code (text), Description (text).
There's no need to display the ID or the Description. We only need to
display the codes, such as Art, Math, HS, or ML.

thanks for your suggestions.

 

[Peter Hibbs]

A Flex Grid Control will probably do what you want but it will involve
a bit of VBA code. Have a look at -

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='Flex Grid Demo.mdb'

for some examples.

Peter Hibbs.

 

[gllincoln]

Hi,

Take a look at the Treeview control. It's a complicated devil to get up and running with but it's exactly what you are describing, apparently what you need.

It's a little disjoint in presentation but towards the middle of the rambling discourse regarding the .NET treeview web control, there are some good code examples.

http://15seconds.com/issue/030827.htm

Hope this helps,
Gordon

 

[Albert D. Kallal]

You might be able to use 2, or 3 sub-forms.

if you look at the last screen shot in the following:
http://www.members.shaw.ca/AlbertKallal/Articles/Grid.htm

You see how I had to display batch run (one - date time etc).

Then I had to display "many" people, and for EACH person display "many"
payments.
(the above is a classic screen in which you take a cheque amount, but
distribute it to SEVERAL accounts).

So, that screen shows a date for data entry, then it also shows many people,
and for each person, it shows many payments distributed to accounts.

That last screen might give you some ideas...

 

[Jeff Boyce]

Are you saying that each Teacher's license can hold multiple endorsements
and each Teacher's License's Endorsement can carry multiple Authorizations?

Another interpretation is that a license could be limited to one-of-many
endorsements, and an endorsement could be limited to one-of-many
Authorizations.

--
Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP


Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

 

[wdsnews]

Are you saying that each Teacher's license can hold multiple endorsements
and each Teacher's License's Endorsement can carry multiple
Authorizations?

Yes. One thing I failed to mention is I'm designing a form to use for both
data entry and data display.

For each Teacher there may be multiple Licenses to enter. For each License
there will be multiple Endorsements. For each Endorsement there will be
multiple Authorizations.

 

[wdsnews]

Thanks Albert.

I agree with you about the advantage of Continuous forms. I also agree with
you about the importance of being able to enter or edit data on a subform.
Data entry is very important for my Teacher application.

My current design uses a subform in a subform in a subform. The deepest
level subform uses "continuous" view mode to display the Authorizations, one
below the previous. Unfortunately, I haven't found a way to nest one
continuous view subform inside another continuous view subform.

Now, if 'forms' permitted the column arrangement like 'reports' allow, it
would then be possible to list Authorizations side by side rather than one
below the previous. But to my knowledge, it isn't possible to display
editable sibling records side by side.

Thanks for the link! I like your articles. (BTW, you'll want to search
your article for "continues" and change them to "continuous".)

 

[wdsnews]

Gordon, thank you.

I agree a treeview arrangement would be ideal. Does this solution allow
data entry as well as data viewing? It's important to allow data entry in
this application.

I haven't yet jumped in to .NET. I'm hoping I'll get a chance this summer.

I especially appreciate the link to 15seconds.com. ....looks like a good
resource. thanks.


Hi,

Take a look at the Treeview control. It's a complicated devil to get up and
running with but it's exactly what you are describing, apparently what you
need.

It's a little disjoint in presentation but towards the middle of the
rambling discourse regarding the .NET treeview web control, there are some
good code examples.

http://15seconds.com/issue/030827.htm

Hope this helps,
Gordon

 

[wdsnews]

Thank you Peter. It looks like you gave me what I asked for.
Unfortunately, I failed to mention that I'm looking for data entry as well
as display. New records will be created down all four levels of the tree.

I like what I see in the FlexGrid solution. I'll hang on to it for the
future. Thank you.

 

[John W. Vinson]

Thanks Albert.

I agree with you about the advantage of Continuous forms. I also agree with
you about the importance of being able to enter or edit data on a subform.
Data entry is very important for my Teacher application.

My current design uses a subform in a subform in a subform. The deepest
level subform uses "continuous" view mode to display the Authorizations, one
below the previous. Unfortunately, I haven't found a way to nest one
continuous view subform inside another continuous view subform.

Now, if 'forms' permitted the column arrangement like 'reports' allow, it
would then be possible to list Authorizations side by side rather than one
below the previous. But to my knowledge, it isn't possible to display
editable sibling records side by side.

Well, it's possible, and may be a worthwhile alternative to the grid control.

What you need to do is use a "relay" textbox on the mainform. Let's say you
want a continuous subform for Endorsements, and next to it a continuous
subform for Authorizations, where the authorizations displayed correspond to
the currently selected Endorsement. To do so, put a textbox
txtRelayEndorsement (its visible property can be set to No so it doesn't
clutter your form) on the form or subform which is the parent of these two;
set its Control Source to

=subEndorsements.Form!txtEndorsementID

using the name of the endorsement's subform control and the name of a control
on that form which contains the linking field.

Then set the Master Link Field property of the Authorizations subform to

=txtRelayEndorsement

You may also need to requery the authorizations subform in the AfterUpdate
event of the Endorsements subform.