Combining a snake report with a normal report

I'm creating a report that will present information split into several
sections with each section dealing with a particular aspect of data.
No problem there. However, one of the sections will contain
photographs which I need to snake across and down the page. That's
fine if the report just contained photos because I can create the
column of an appropriate width and let the report get on with it. But,
because those sections of the report that are not photos need to be
full width, I don't see how I can combine the two. Perhaps with a sub-
report (I'm not sure and this Access Bible I've got here says nothing
about sub-reports)?? All advice welcome, please

Many thanks

Re: Combining a snake report with a normal report

On Jan 12, 8:28=A0am, anthony wrote:
> I'm creating a report that will present information split into several
> sections with each section dealing with a particular aspect of data.
> No problem there. However, one of the sections will contain
> photographs which I need to snake across and down the page. That's
> fine if the report just contained photos because I can create the
> column of an appropriate width and let the report get on with it. But,
> because those sections of the report that are not photos need to be
> full width, I don't see how I can combine the two. Perhaps with a sub-
> report (I'm not sure and this Access Bible I've got here says nothing
> about sub-reports)?? All advice welcome, please
>
> Many thanks

For sub reports, just create a separate report for each one of the
sections. Then create another report and drag each section report
in. Resize and rearrange as you like. In the main report the sub
reports can be super thin and stretch all the way across the page, and
when you actually view them they will grow to their full length (by
default).

Re: Combining a snake report with a normal report

OK, groovy. I'll do some experimentation. Thanks very much

Re: Combining a snake report with a normal report

I can't get this to work and it's driving me bananas. I have a main
report with the detail section consisting just of a subreport. The
subreport is supposed to snake, and it does when opened on its own.
However, when added as a subreport to the main report, it doesn't
snake. It provides all the right data but doesn't snake. If I remove
the master/child links, it snakes but obviously produces rubbish. I am
at my wits end - Access 2007, by the way

Re: Combining a snake report with a normal report

What exactly is "snake"? I gather you want some photos on a report, but are
those same or related photos supposed to go onto another report? Would you
cite an example of what you are trying to achieve as an end result?

Just curious...
Earl


"anthony" wrote in message
news:6996c705-75da-418b-b832-6858d948a502@e23g2000prf.google groups.com...
>I can't get this to work and it's driving me bananas. I have a main
> report with the detail section consisting just of a subreport. The
> subreport is supposed to snake, and it does when opened on its own.
> However, when added as a subreport to the main report, it doesn't
> snake. It provides all the right data but doesn't snake. If I remove
> the master/child links, it snakes but obviously produces rubbish. I am
> at my wits end - Access 2007, by the way

Re: Combining a snake report with a normal report

A snake report is one that consists of columns (two in my case). You
can configure the data to go down each column, then across to the top
of the next column and down that etc, or across each row, down to the
beginning of the next row and across that and so on

Part of my report consists of photos and I want six photos on the page
in two columns, hence the need for a snake report

EXCEPT, I can't get it to snake!

Re: Combining a snake report with a normal report

To create a Snake Report, you go into the menu item "File/Page Setup", click
on the Columns tab. In this case you'd type in that you want 2 columns.
Make the report width small enough to fit inside 2 columns.

You'd want to do this in a SubReport because the majority of the report is
single column.

I hope this helps.


Dominic

"anthony" wrote in message
news:c50c2c3c-2bf8-4fec-9de9-72b2a44cbb10@q39g2000hsf.google groups.com...
> I'm creating a report that will present information split into several
> sections with each section dealing with a particular aspect of data.
> No problem there. However, one of the sections will contain
> photographs which I need to snake across and down the page. That's
> fine if the report just contained photos because I can create the
> column of an appropriate width and let the report get on with it. But,
> because those sections of the report that are not photos need to be
> full width, I don't see how I can combine the two. Perhaps with a sub-
> report (I'm not sure and this Access Bible I've got here says nothing
> about sub-reports)?? All advice welcome, please
>
> Many thanks

Re: Combining a snake report with a normal report

Hi Dominic

Getting the subreport on its own to snake isn't the problem. It snakes
beautifully. What it won't do is snake when added as a subreport.
Interestingly, it will snake as part of the main report if you remove
the master/child links but then, of course, the data is rubbish

Re: Combining a snake report with a normal report

anthony wrote:
> Hi Dominic
>
> Getting the subreport on its own to snake isn't the problem. It snakes
> beautifully. What it won't do is snake when added as a subreport.
> Interestingly, it will snake as part of the main report if you remove
> the master/child links but then, of course, the data is rubbish
>

Is it possible your subreport, on the main report, is too small? For
example, is it as wide as the main report? Is your column width setting
sufficient? Are your margins in the subreport different than the main
report? I wouldn't have an idea what the link fields would have to do
with anything in making it work or fail.

Maybe you can describe how you are doing this. Are the images
hyperlinks or are then stored in the table? If you provided suffiecent
(but not overwhelming) detail, maybe one of us can recreate a similar
report the way you are doing and see what's happening.

Re: Combining a snake report with a normal report

OK, 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. It makes no difference whether the subreport is the
full width of the main report or narrower

I'm stumped

Re: Combining a snake report with a normal report

anthony wrote:
> OK, two tables: tblCat (CatID, RegNo*, Aol*, Term*) and tlnkCATPhoto
> (CatID*, PhotoID*, Activity, SortOrder) Note: * = primarykey
>
> The query returns all the fields.

From what table? I'll assume tblCat is the main table. Do you have 2
CatID fields in the query?

The main report groups on RegNo
> (header only and no fields), then Aol (Aol field), There are two
> further sorts: SortOrder, followed by PhotoID.

Why is PhotoID required in the main report?

The page header
> contains RegNo.

That's it? What about CatID? Maybe create a group with a header on
RegNo and move your RegNo and CatID to the header band.

The detail section comprises the subreport, which,
> itself, is bound to the same query.

Why?

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. It makes no difference whether the subreport is the
> full width of the main report or narrower
>
> I'm stumped

OK. And what is PhotoID? Is it a number? Or is it an image? I should
think if it's a text field that would be no problem. I posted a
solution for that last week for a snaking subreport.

I think your report, as it is, is too complex. I would create a main
report with just the fields I need. I would create a subreport that has
just the fields that I need that also has a link field to the main report.

I would do absolutely no sorting with the recordsource/query but only
from the Sorting*Grouping option.

Re: Combining a snake report with a normal report

>> From what table?

All the fields from both tables are in the query

>> Why is PhotoID required in the main report?

Are you saying that it would be better to sort PhotoID in the
subreport?

>> Maybe create a group with a header on RegNo

There is a group on RegNo (no fields); I need RegNo to appear on every
page which is why it's in the page header

>> And what is PhotoID? Is it a number?

It's an AutoNumber


>> I would create a main report with just the fields I need.
>> I would create a subreport that has just the fields that
>> I need that also has a link field to the main report

That's exactly what I've done. I've only got two fields on the main
report and two on the subreport. All sorting takes place in the report

>> I posted a solution for that last week for a snaking subreport.

Do you remember the subject (so I can search for it)?

TVM

Re: Combining a snake report with a normal report

anthony wrote:

>>>From what table?
>
> All the fields from both tables are in the query

Why?

>>>Why is PhotoID required in the main report?
>
> Are you saying that it would be better to sort PhotoID in the
> subreport?

Yes.

For the main report my recordsource would be
Select CatID, Regno from tblCat
That's it.

My subreports recordsource would be
select catid, photoId, sortorder from tlnkCATPhoto
That's it.

I would go into sorting&grouping to set your sort for both reports.

I would create a group header in the main report and drop in both catid
and regno. catid can be set visible = false in you don't want to see
it. Same with regno.


You link master/child should be on CatID if I'm reading your structure
correctly.

>>>Maybe create a group with a header on RegNo
>
> There is a group on RegNo (no fields); I need RegNo to appear on every
> page which is why it's in the page header

That's why Group headers have RepeatSection in the format tab. Create a
group header, click on the band to get the property sheet, click on
Format. Press F1 on Repeat Section.

>>>And what is PhotoID? Is it a number?
>
> It's an AutoNumber
>
Fine. All you are printing are snaking numbers. No big deal. Should
be fine.

>>>I would create a main report with just the fields I need.
>>>I would create a subreport that has just the fields that
>>>I need that also has a link field to the main report
>
> That's exactly what I've done. I've only got two fields on the main
> report and two on the subreport. All sorting takes place in the report
>
Then something is being done incorrectly.

>>>I posted a solution for that last week for a snaking subreport.
>
> Do you remember the subject (so I can search for it)?
>

I looked at. Not as much detail as I've been providing.

I suggest you start over. Create a main report with just the fields
from the main table. Drop in CatID and Regno.

Create a report from the link table, make it multicolumn and do your
sorts there. Then drop it into the main report and set the link to
CatID. I can guarantee you are doing something incorrectly.

BTW, what version of Access are you using?

Re: Combining a snake report with a normal report

>> BTW, what version of Access are you using?

2007

Very good advice; I'll look at that carefully, re-jig and report back.
Very grateful for your help

Re: Combining a snake report with a normal report

"anthony" wrote in message
news:bc84d0b5-7020-4a51-aabc-c54950e5ff07@q39g2000hsf.google groups.com...
>A snake report is one that consists of columns (two in my case). You
> can configure the data to go down each column, then across to the top
> of the next column and down that etc, or across each row, down to the
> beginning of the next row and across that and so on
>
> Part of my report consists of photos and I want six photos on the page
> in two columns, hence the need for a snake report
>
> EXCEPT, I can't get it to snake!

A "snaking columns" report, embedded in a Subreport Control, only works if
the order is "Accross Then Down".

Larry Linson
Microsoft Access MVP

Re: Combining a snake report with a normal report

>> only works if the order is "Accross Then Down".

....which is fortunate as that is the order I want!

Re: Combining a snake report with a normal report

Hallelujah! Salad has it!

Re: Combining a snake report with a normal report

anthony wrote:
> Hallelujah! Salad has it!

Not sure what I have. :)

Hip Hip Hurray!
http://www.youtube.com/watch?v=bXk5PWs0EEs

Re: Combining a snake report with a normal report

"Salad" wrote

>> Hallelujah! Salad has it!
>
> Not sure what I have. :)

If everybody is screaming and fleeing away, I don't want to know.

If it is young people of the opposite sex, screaming and stampeding toward
you, you have "star power", Salad.

:-)