Can I have siblings in a banded data access page?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to build a data access page that has a top level section with data from one table and multiple banded sections, each of which is subordinate to the top level. What seems to be easy to do within the Access Pages GUI is to create a report that has a parent-child-grandchild-greatgrandchild... structure, but what I can't figure out how to create is a parent-child1,child2,... structure.

I think this restriction exists in Access reports and the VB report objects as well, but I don't have much memory of a work-around, if there even is one.

I'd like to avoid script if at all possible and just use the drag-and-drop features of the Pages GUI.

Any help is gratefully appreciated!

thanks,
mark hinnebusch
 
From the Access help file (XP version)
A subform is a form that is inserted in another form. The primary form is
called the main form, and the form within the form is called the subform. A
form/subform combination is often referred to as a hierarchical form, a
master/detail form, or a parent/child form.

Subforms are especially effective when you want to show data from tables or
queries with a one-to-many relationship. For example, you could create a
form with a subform to show data from a Categories table and a Products
table. The data in the Categories table is the "one" side of the
relationship. The data in the Products table is the "many" side of the
relationship - each category can have more than one product...



It goes on from there. Look up subform in the help file.


--
Joseph E. Meehan

26 + 6 = 1 It's Irish Math


Mark Hinnebusch said:
I am trying to build a data access page that has a top level section with
Click to expand...
data from one table and multiple banded sections, each of which is
subordinate to the top level. What seems to be easy to do within the Access
Pages GUI is to create a report that has a
parent-child-grandchild-greatgrandchild... structure, but what I can't
figure out how to create is a parent-child1,child2,... structure.
I think this restriction exists in Access reports and the VB report
Click to expand...
objects as well, but I don't have much memory of a work-around, if there
even is one.
 
Joseph,

Thanks for your quick reply. My problem is being able to have two children of a parent on the same form. You can have multiple subforms in Access forms, but in Access Data pages, it seems to use the report model that only allows one child per parent. (But I am hoping that I am wrong about this, hence my question.)

thanks,
mark
 
I believe you are wrong, if I understand what you want. Try using a
tabular form for the child.

--
Joseph E. Meehan

26 + 6 = 1 It's Irish Math


Mark Hinnebusch said:
Joseph,

Thanks for your quick reply. My problem is being able to have two
Click to expand...
children of a parent on the same form. You can have multiple subforms in
Access forms, but in Access Data pages, it seems to use the report model
that only allows one child per parent. (But I am hoping that I am wrong
about this, hence my question.)
 
Joseph,

Here is my situation. I have a table of test cases.
Associated with each test case is a set of files. Also
associated with each test case is a set of prerequisites.
There is no relationship between the files and the
prerequisites, so they share no common key. However,
they both relate to the test case record and each tables
prime key is a foreign key in the test case record.

The parent record in the web form is to be the test case
record. I want two banded sections, one for the files and
one for the prerequisites. The GUI lets me create a
banded section for the files, under the test case record,
but will only let me create the prerequisite section as a
child of the files section, not the test case section,
which is what I need and which properly reflects the
structure of the database. Alternately, I can create a
banded section for the prerequisites under the test case
section, but then the files section insists on being
subordinate to the prerequisites section, again, not what
is needed.

I didn't understand your suggestion. If my explanation
above matches what you understand of my problem, then can
you elaborate a bit on your suggestion?

thanks!
mark
 
Well if I am reading you right, you should be able to set up a 1-many
relationship between files(many) and Test Cases(1) and a 1-many relationship
between prerequisites(many) and Text Cases(1). Then it is just a matter of
creating a form with two child forms.
 
You are reading it right and those relationships do
exist. With access forms, I can have multiple child forms
and can easily do what I need. With data access pages,
however, I can't figure out how to have two child forms.
That is the crux of my problem.

thanks,
mark
 
Thanks for trying. There aren't many people who take the
time to respond on these lists and I appreciate your
efforts.

I guess I will have to do it in VB instead of using data
access pages. It looked like an easy way to go.

thanks, again,
mark
 
Back
Top