Getting a snake subreport to snake!

[anthony]

I'm designing a report, the details section of which (and only the
details
section) needs to snake over two columns (across, then down). I
thought a
subreport would do it but although the subreport snakes when opened on
its
own, it does not snake when added as a subreport with the master/
child
links set. If you remove the master/child links, the report *will*
snake
but of course the data is rubbish.

How do I get part of a report to snake?

(Using Access 2007)

 

[Duane Hookom]

"needs to snake over two columns (across, then down)" this is exactly how you
should set up the columns in your subreport. Are you sure you don't want your
columns to display down, then across?

 

[Marshall Barton]

I'm designing a report, the details section of which (and only the
details
section) needs to snake over two columns (across, then down). I
thought a
subreport would do it but although the subreport snakes when opened on
its
own, it does not snake when added as a subreport with the master/
child
links set. If you remove the master/child links, the report *will*
snake
but of course the data is rubbish.

How do I get part of a report to snake?

It sounds like the subreport's snaking is set to down then
across.

 

[anthony]

"needs to snake over two columns (across, then down)" this is exactly how you
should set up the columns in your subreport. Are you sure you don't want your
columns to display down, then across?

The subreport is setup for two columns. Across then down is what I
need. The report will snake when run on its own but not when added as
a subreport to the main report.

Further details are:

Two tables: tblCat (CatID, RegNo*, Aol*, Term*) and tlnkCATPhoto
(CatID*, PhotoID*, Activity, SortOrder) Note: * = primarykey

The query returns all the fields. The main report groups on RegNo
(header only and no fields), then Aol (Aol field), There are two
further sorts: SortOrder, followed by PhotoID. The page header
contains RegNo. The detail section comprises the subreport, which,
itself, is bound to the same query. The subreport only has a detail
section which contains PhotoID and Activity; there are no page or
report headers. It's set to have two columns and to go across then
down. The master/child links are on PhotoID


The margins for both reports are the same. The subreport snakes when
run on its own but not when part of the main report. It makes no
difference
whether the subreport is the full width of the main report or
narrower

I'm stumped

 

[anthony]

It sounds like the subreport's snaking is set to down then
Definitely across then down

 

[Duane Hookom]

I think your issue might be
========================
bound to the same query. The subreport only has a detail
section which contains PhotoID and Activity; there are no page or
report headers. It's set to have two columns and to go across then
down. The master/child links are on PhotoID
=========================
Normally the main report does not have the same level of detail as the
subreport. I would not expect the main report to have the tlnkCATPhoto table.
The detail level of the main report would be CatID and the CatID would be
used to join the main and subreport.

 

[anthony]

OK, got you. I'll adjust and report back. Appreciate your help

 

[Marshall Barton]

Definitely across then down

I have never heard of, much less seen an across then down
snaking report/subreport only go down without using the 2nd
column. There must be something more to this than what
you've said so far.

I see that Duane has dug deeper into what you are doing so I
should just bow out before I confuse the issue.

 

[anthony]

Yeah, on the button Duane. Very many thanks