Force New page for new group

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

Guest

Hi- I have a report based on a query. The query has three relevant fields,
MAKE and MODEL and TERM, and the query sorts in that order, first by MAKE and
then by MODEL and then TERM. What I am getting now on the report is one
MAKE, followed by the models, and the TERMs for each MODEL. There can be
between 4 and 6 TERMs for each MODEL. What I would like is to have the MODEL
be forced on to a new page if all of it's terms won't fit on the page. This
is how they lay out now:
TERM
Make
Model
24
30
36
48

MAKE
MODEL
24
27
30
36
39
48

etc, etc.

I'd like to have multiple MODELS on the page but I want to make sure that I
don't have 24 and 30 at the bottom of the page, and have 36 and 48 at the top
of the next page. I would rather have that MODEL ALL on the next page. How
can I accomplish this?

Any help would be greatly appreciated.

Gary in Michigan, USA
 
Try setting the "Keep together" property for the group (View | Sorting and
Grouping) to Yes.
 
Gary,
Try using the KeepTogether option for your "break" field via the Sorting
and Grouping dialog box.
 
That worked, grouping on the Model! Now I have one other minor problem I
hope someone can help with. One of the fields on the report is a text field
and sometimes has more data than there is room on line so we end up getting
two pages printed for every page, and the 2nd page only has a few characters
on it. I would like to be able to trim the data in that field so that the
2nd (un-needed) page doesn't display or print.

Thanks so much for your help.
 
Gary,
If the field were named MyText, then =Left(MyText,100) would always yield
100 characters or less.
 
Al,

I put the following in the Control Source of the textbox on the report:

=Left([Message],110)

"Message" is the field. Acess returns #error. If I leave the Control
Source as [Message] the message displays. Was I supposed to put this code
elsewhere?

Thanks for your help.
 
Hmmm... That's really odd. It should work.

First, don't name the field Message. Since you now have an unbound
calculated field, you can't use the actual field name. Call it txtMessage.
I bet that's it.

If not...
Try putting this column in your report query...
ShortMsg : Left([Message],110)
then place ShortMsg on the report instead of the unbound calculation. Run
the query, and see if that works.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

GaryS said:
Al,

I put the following in the Control Source of the textbox on the report:

=Left([Message],110)

"Message" is the field. Acess returns #error. If I leave the Control
Source as [Message] the message displays. Was I supposed to put this code
elsewhere?

Thanks for your help.
--
Gary in Michigan, USA


Al Camp said:
Gary,
If the field were named MyText, then =Left(MyText,100) would always
yield
100 characters or less.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions
Click to expand...
Click to expand...
 
Al,

Oh stupid me. I generally follow the convention of naming textbox controls
with the prefix txt for forms, but I have neglected to do so with reports.
Live and learn, that solved the problem. Thanks so much!!
--
Gary in Michigan, USA


Al Camp said:
Hmmm... That's really odd. It should work.

First, don't name the field Message. Since you now have an unbound
calculated field, you can't use the actual field name. Call it txtMessage.
I bet that's it.

If not...
Try putting this column in your report query...
ShortMsg : Left([Message],110)
then place ShortMsg on the report instead of the unbound calculation. Run
the query, and see if that works.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

GaryS said:
Al,

I put the following in the Control Source of the textbox on the report:

=Left([Message],110)

"Message" is the field. Acess returns #error. If I leave the Control
Source as [Message] the message displays. Was I supposed to put this code
elsewhere?

Thanks for your help.
--
Gary in Michigan, USA


Al Camp said:
Gary,
If the field were named MyText, then =Left(MyText,100) would always
yield
100 characters or less.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

That worked, grouping on the Model! Now I have one other minor problem
I
hope someone can help with. One of the fields on the report is a text
field
and sometimes has more data than there is room on line so we end up
getting
two pages printed for every page, and the 2nd page only has a few
characters
on it. I would like to be able to trim the data in that field so that
the
2nd (un-needed) page doesn't display or print.

Thanks so much for your help.
--
Gary in Michigan, USA


:

Gary,
Try using the KeepTogether option for your "break" field via the
Sorting
and Grouping dialog box.
--
hth
Al Camp
Candia Computer Consulting - Candia NH
http://home.comcast.net/~cccsolutions

Hi- I have a report based on a query. The query has three relevant
fields,
MAKE and MODEL and TERM, and the query sorts in that order, first by
MAKE
and
then by MODEL and then TERM. What I am getting now on the report is
one
MAKE, followed by the models, and the TERMs for each MODEL. There
can
be
between 4 and 6 TERMs for each MODEL. What I would like is to have
the
MODEL
be forced on to a new page if all of it's terms won't fit on the
page.
This
is how they lay out now:
TERM
Make
Model
24
30
36
48

MAKE
MODEL
24
27
30
36
39
48

etc, etc.

I'd like to have multiple MODELS on the page but I want to make sure
that
I
don't have 24 and 30 at the bottom of the page, and have 36 and 48
at
the
top
of the next page. I would rather have that MODEL ALL on the next
page.
How
can I accomplish this?

Any help would be greatly appreciated.

Gary in Michigan, USA
Click to expand...
Click to expand...
Click to expand...
 
Back
Top