Sandra,
The problem I don't like nested subforms is that when you
have more 2 layers of subforms, you can not display in
datasheet view.
For example:
On the main form, I display records from the division
table.
On the tier one subform (subform directly embedded in the
main form), I have the list of processes that correspond
to the division that is being displayed on the main form
(link field: divisionid). Then within the process subform
(or subform tier 1), I have another subform showing
subprocesses corresponding to a specific process selected
in the process subform.
After I add the the subprocess subform within the process
subform, the process subform no longer be able to display
in datasheet view.
This is ugly because users have to scroll down or up or
click the record navigator for the process subform to
select process.
So instead I try to use unbound listbox or combo box to
navigate. My idea is I create say a combo box with row
source pointing to DivisionId, the DivisionName field in
the Division table. I create another combo box with row
source set to the Processid, ProcessName fields in the
process table. When I select a specific division in the
first combo box, the available choices in the Process
combo box should narrow down to only those related to the
division I selected in the first combo box...in this way,
if I add another combo box called subprocess, I will be
able to navitage to a specific subprocess and then
view/edit it.
I find it hard to narrow down selections in subsequent
combo boxes based on value selected in previous combo box.
Could you help me out?
Thanks
Thomas
-----Original Message-----
Sure, there are plenty of ways - you can use synchronized subforms
(continuous subform which is synchronized with a subform showing record
details), Listbox and subform, TreeView control (not the easiest to
implement unless you are comfortable with VBA but very doable). You could
also do a chain of pop-up forms (though this wouldn't be my preference in
most situations).
What type of data are you displaying and what is wrong with subforms? FWIW,
the ability to use subforms is one of the strengths of Access.
--
Sandra Daigle
[Microsoft Access MVP]
For the benefit of others please post all replies to this newsgroup.
Hi,
I am trying to build something like a navigator so that
users can navigate through cascaded records based on one-
to-many tables.
I know one way is to build main form, subform tier one,
subform tier 2 (within the previous subform), subform tier
3.... and make the fields you don't want user to update
readonly.
Are they any better and easier way to accomplish the same
task?
Thanks
.
