Columnar sub-report in a non-columnar Detail section

  • Thread starter Thread starter hunarch via AccessMonster.com
  • Start date Start date
H

hunarch via AccessMonster.com

How can one insert a columnar sub-report (established by using Page Setup) in
the Detail section of a report where other Detail fields need to be non-
columnar? No headings are required.
 
hunarch said:
How can one insert a columnar sub-report (established by using Page
Setup) in the Detail section of a report where other Detail fields
need to be non- columnar? No headings are required.
Click to expand...

Just do it.

Multi-column subreports have to be either displayed in a subreport control
that has CanGrow set to No or use "Across, Then Down" column snaking. If
you use "Down, Then Across" you will get one continuous column because the
subreport does not "know" when the parent report hits the bottom of page.
 
Thanks for replying Rick.
In the subreport, text field height = 0.01, can grow=yes.
Sub-report columns have been tried 1) across-then-down and, 2) down-then
across plus, after insertion in main report, the subreport's controls set to
can grow = no.
I have also played around with widths of the subreport in the master report.
Whichever way, the result is mono-columnar not multi-columnar.
Another suggestion I came across was to start with a new master report in
case the original is corrupted. I tried that, but with no greater success.
I have also tried setting the multi-columnar format for the subreport, not
ony before but also after its insertion in the main report, but the latter
then makes the main report multi-columnar (although the page and report
headers remain mono-columnar - even the MS KB article and the examples in
Northwind infer that this is the only way of achieving columnar reports [i.e.
relying upon the page header to remain mono-columnar]).
Any more suggestions?

Rod
 
hunarch said:
Thanks for replying Rick.
In the subreport, text field height = 0.01, can grow=yes.
Sub-report columns have been tried 1) across-then-down and, 2)
down-then across plus, after insertion in main report, the
subreport's controls set to can grow = no.
I have also played around with widths of the subreport in the master
report. Whichever way, the result is mono-columnar not multi-columnar.
Another suggestion I came across was to start with a new master
report in case the original is corrupted. I tried that, but with no
greater success.
I have also tried setting the multi-columnar format for the
subreport, not ony before but also after its insertion in the main
report, but the latter then makes the main report multi-columnar
(although the page and report headers remain mono-columnar - even the
MS KB article and the examples in Northwind infer that this is the
only way of achieving columnar reports [i.e. relying upon the page
header to remain mono-columnar]).
Any more suggestions?

Rod
Click to expand...

If you have an Across, Then Down report that will snake correctly when opened as
a separate report then it should still work that way when inserted as a
subreport. I've never seen a problem with that.
 
If you have an Across, Then Down report that will snake correctly when opened as

Frustrating. It can't be much simpler. But, it's still not working!
Is there some other setting I should be using? Is there something that I
might not have done that is really, really obvious - to most people!
Rod
 
I'm not sure what result you are experiencing. Does your subreport display
multiple records? If so, I assume the subreport records display in a single
column. What are these properties:

Subreport:
Width:
Column Count:
Across Then Down or
Down then Across:

Subreport Control on main form:
Link Master:
Link Child:
Width:
Can Grow:
Can Shrink:

Main report
Width:

Section of main report containing subreport:
Can Grow:
Name of section:
 
Thanks Duane.
My responses are in square brackets in your reply below.

Duane said:
I'm not sure what result you are experiencing. Does your subreport display
multiple records? [Yes] If so, I assume the subreport records display in a single
column. [Subreport is correctly multi-columnar, but changes to mono-columnar when inserted in main report]. What are these properties:

Subreport: [name: "rpt_Lctn_Sub"]
Width: [text field = 5cm; located in Detail section. There are no other fields in the subreport.]
Column Count: [3 columns, each column at 5cm with 0.5 cm column spacing]
Across Then Down or
Down then Across: [Across then down]

Subreport Control on main form[report]:
Link Master: [LocationID]
Link Child: [LocationID] [Source object = Report.rpt_Lctn_Sub]
Width: [18cm]
Can Grow: [Yes]
Can Shrink: [Yes]

Main report
Width: [A4 (19cm). Margins set at minimum allowed by printer (4mm)]

Section of main report containing subreport:
Can Grow: [Tried "Yes" and "No"]
Name of section: [Detail]
[quoted text clipped - 3 lines]
might not have done that is really, really obvious - to most people!
Rod
Click to expand...
Click to expand...
 
hunarch said:
Frustrating. It can't be much simpler. But, it's still not working!
Is there some other setting I should be using? Is there something
that I might not have done that is really, really obvious - to most
people! Rod
Click to expand...

The report does snake the columns properly when opened as a separate report
right?
 
The report does snake the columns properly when opened as a separate report
right?
Click to expand...
Yes, thanks Rick. In fact, I am using it successully now with a Table of
Contents where I have 3 nested subreports main report (in the Detail).
Each subreport formats correctly (i.e. multi-columnar) as does the main
report. All subreports and the main report have their page set-up fixed to
the desired number of columns (2 in this instance). I have the snaking going
down then across in this case because, I am guessing, there is only a page
and report header and footer each side of the Detail section - which I
believe is why the columnisation in the main report is working.
However, the problem I am still grappling occurs in another report where
there are other headers and footers between the Detail section and the
page/report headers/footers. There are also mono-columnised fields in the
Detail section as well as the intended multi-columnar fields via the
subreports.
Rod
PS Thanks to Steven Lebans for his dotted leader code!
 
By itself, does the subreport print across then down? When the subreport
changes to mono-columnar when inserted in the main report can we assume you
are still seeing multiple records?

If the answers above are Yes and Yes then I would attempt to recreate the
report and subreport.

--
Duane Hookom
MS Access MVP

hunarch via AccessMonster.com said:
Thanks Duane.
My responses are in square brackets in your reply below.

Duane said:
I'm not sure what result you are experiencing. Does your subreport display
multiple records? [Yes] If so, I assume the subreport records display in a
single
column. [Subreport is correctly multi-columnar, but changes to
mono-columnar when inserted in main report]. What are these properties:

Subreport: [name: "rpt_Lctn_Sub"]
Width: [text field = 5cm; located in Detail section. There are no
other fields in the subreport.]
Column Count: [3 columns, each column at 5cm with 0.5 cm column
spacing]
Across Then Down or
Down then Across: [Across then down]

Subreport Control on main form[report]:
Link Master: [LocationID]
Link Child: [LocationID] [Source object = Report.rpt_Lctn_Sub]
Width: [18cm]
Can Grow: [Yes]
Can Shrink: [Yes]

Main report
Width: [A4 (19cm). Margins set at minimum allowed by printer (4mm)]

Section of main report containing subreport:
Can Grow: [Tried "Yes" and "No"]
Name of section: [Detail]
If you have an Across, Then Down report that will snake correctly when
opened as
Click to expand...
[quoted text clipped - 3 lines]
might not have done that is really, really obvious - to most people!
Rod
Click to expand...
Click to expand...
Click to expand...
 
<I would attempt to recreate the report and subreport.

I have just now done that again. New subreport formats across then down. When
inserted in new main report, the formatting reverts to a single column! It's
as if the Page Setup of the main report over-rides the Page Setup of the
subreport.
Again, in the subreport, the width of text field and the underlying page in
design view is set to column width. In the main report, the width of the
subreport after insertion has been tried at the full width of the main report
and at the width of the column - without any difference in the single-column
result.
 
<I would attempt to recreate the report and subreport.

I have just now done that again. New subreport formats across then down. When
inserted in new main report, the formatting reverts to a single column -
without loss of data! It's as if the Page Setup of the main report over-rides
the Page Setup of the subreport.
Again, in the subreport, the width of text field and the underlying page in
design view is set to column width. In the main report, the width of the
subreport after insertion has been tried at the full width of the main report
and at the width of the column - without any difference in the single-column
result.
Could you confirm that multi-columnar formatting formating (via subreports)
should be achievable (e.g in the Detail section) even if:
1) there are headers/footers additional to report/page headers/footers, and
2) there are also mono-columnar fields in the Detail section?
Thanks for your persistance. This is a vital element in my report.
 
hunarch said:
<I would attempt to recreate the report and subreport.

I have just now done that again. New subreport formats across then
down. When inserted in new main report, the formatting reverts to a
single column - without loss of data! It's as if the Page Setup of
the main report over-rides the Page Setup of the subreport.
Again, in the subreport, the width of text field and the underlying
page in design view is set to column width. In the main report, the
width of the subreport after insertion has been tried at the full
width of the main report and at the width of the column - without any
difference in the single-column result.
Could you confirm that multi-columnar formatting formating (via
subreports) should be achievable (e.g in the Detail section) even if:
1) there are headers/footers additional to report/page
headers/footers, and 2) there are also mono-columnar fields in the
Detail section?
Thanks for your persistance. This is a vital element in my report.
Click to expand...

Does the linking field between main and subreport produce more than one
record in the subreport?

My guess is that you are seeing multiple *instances* of the subreport with
each one having a single record. Obviously multi-column settings will have
no effect on a report that is only returning a single record.
 
<I would attempt to recreate the report and subreport.
My guess is that you are seeing multiple *instances* of the subreport with
each one having a single record. Obviously multi-column settings will have
no effect on a report that is only returning a single record.
Click to expand...
Bingo. I can now see that what you have guessed is in fact the case because
in my last attempt I left the solid line around the subreport: the result is
that whilst some boxes have only one record, others have several records - in
a multi-columnar format within the box!! Choosing the correct parent and
child fields is obviously my next task.
Many thanks Rick and Duane.
 
Many thanks Rick and Duane.Post-script.
My linking was on the correct fields. However, my problem was solved by :
1) In the subreport, invoking a SQL statement, inserting a Totals row and
accepting its default "Group by" condition
2) In the main report:
a. creating a footer corresponding with the data of the field (i.e.
apologies for sloppy description)
b. relocating the subreport from the Detail section to the new Footer.
 
Back
Top