Columns in a subreport DO NOT Snake

[kbrad28 via AccessMonster.com]

I have discovered an KB article "Columns in a subreport DO NOT Snake" that
has helped me change the detail section of a report. Now the problem that I
am having is that once the widths of the columns has been set in the report
the second column info is cut off...I have tried various change but no luck.
Has anyone else has this type of problem after using the article found here
(support.microsoft.com/kb/212748)? Or any suggestions on how to shrink some
of the white space that is being created? Thanks in advance.


Kbrad28

 

[Golfinray]

Have you tried going to file\page setup\page and adjusting the size of your
report? You may have to go landscape or go to a larger size paper.

 

[Marshall Barton]

I have discovered an KB article "Columns in a subreport DO NOT Snake" that
has helped me change the detail section of a report. Now the problem that I
am having is that once the widths of the columns has been set in the report
the second column info is cut off...I have tried various change but no luck.
Has anyone else has this type of problem after using the article found here
(support.microsoft.com/kb/212748)? Or any suggestions on how to shrink some
of the white space that is being created? Thanks in advance.

Check to make sure that your report fits within the column
width or uncheck the Same As Detail box and manually set the
column width to less than half the available paper width.

 

[kbrad28 via AccessMonster.com]

Thanks alot for the speedy response...I have corrected my problem, but not
it's only snaking if one record has more data then another...is there a way
to snake all records no matter how much data is listed in each record?

I have discovered an KB article "Columns in a subreport DO NOT Snake" that
has helped me change the detail section of a report. Now the problem that I

[quoted text clipped - 3 lines]

(support.microsoft.com/kb/212748)? Or any suggestions on how to shrink some
of the white space that is being created? Thanks in advance.

Check to make sure that your report fits within the column
width or uncheck the Same As Detail box and manually set the
column width to less than half the available paper width.

 

[Marshall Barton]

Thanks alot for the speedy response...I have corrected my problem, but not
it's only snaking if one record has more data then another...is there a way
to snake all records no matter how much data is listed in each record?

I don't follow that. Could you explain what you mean by
"snaking", what is actually happening and what you want to
happen?

 

[kbrad28 via AccessMonster.com]

Snaking --
Info 1 Info 4
Info 2 Info 5
Info 3 Info 6

This is what I am trying to achieve.

If one record has less info in it I get a single column instead of 2.

 

[Marshall Barton]

Snaking --
Info 1 Info 4
Info 2 Info 5
Info 3 Info 6

This is what I am trying to achieve.

If one record has less info in it I get a single column instead of 2.

What does "one record has less info in it" mean?

If you mean that the Down then Across snaking produces
columns of different heights, then use Across then Down
snaking.

 

[kbrad28 via AccessMonster.com]

Ok, let see if I can explain
I have create a recipe database and I have managed to create a subreport to
do the following:
3/4 cups whole milk 3/4 cup canned pumpkin (pure
pumpkin)
3 tablespoons granulated sugar 3/4 teaspoon pumpkin pie spice

3 cups vanilla ice cream GARNISH
canned whipped cream

The problem that I have having now...is if one of my recipes have less
entries to actually make a column it just creates a single column instead of
two. Is there a way to force two columns no matter how many entries?

I hope this helps.

Snaking --
Info 1 Info 4

[quoted text clipped - 12 lines]
What does "one record has less info in it" mean?

If you mean that the Down then Across snaking produces
columns of different heights, then use Across then Down
snaking.

 

[Marshall Barton]

Why doesn't Across then Down snaking meet your needs?
--
Marsh
MVP [MS Access]

Ok, let see if I can explain
I have create a recipe database and I have managed to create a subreport to
do the following:
3/4 cups whole milk 3/4 cup canned pumpkin (pure
pumpkin)
3 tablespoons granulated sugar 3/4 teaspoon pumpkin pie spice

3 cups vanilla ice cream GARNISH
canned whipped cream

The problem that I have having now...is if one of my recipes have less
entries to actually make a column it just creates a single column instead of
two. Is there a way to force two columns no matter how many entries?

Snaking --
Info 1 Info 4

[quoted text clipped - 12 lines]

"snaking", what is actually happening and what you want to
happen?

What does "one record has less info in it" mean?

If you mean that the Down then Across snaking produces
columns of different heights, then use Across then Down
snaking.