Why is my access report page numbering wrong (i.e. Page 13 of 12)?

[Guest]

My page numbering in my access 2003 report is all goofy. It's showing a total
of 12 pages but the last page says 13 of 12. There are 13 pages in all. I am
using the automatic page numbering [Page] & [Pages]. I am canceling some
group totaling events based on data meeting a certain criteria for that
level. Is this the cause? How can I work around this?

 

[Allen Browne]

Yes, code in the event procedures is likely to cause these numbering
problems.

The solution is to exclude the records from the report's source query
instead of suppressing them with the events.

 

[Guest]

Actually I am supressing a group total, not a record.

Yes, code in the event procedures is likely to cause these numbering
problems.

The solution is to exclude the records from the report's source query
instead of suppressing them with the events.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

My page numbering in my access 2003 report is all goofy. It's showing a
total
of 12 pages but the last page says 13 of 12. There are 13 pages in all. I
am
using the automatic page numbering [Page] & [Pages]. I am canceling some
group totaling events based on data meeting a certain criteria for that
level. Is this the cause? How can I work around this?

 

[Allen Browne]

Is there any way to suppress the entries themselves, instead of suppressing
the section?

For example, if you want to suppress the entry if there are fewer than 10,
the control source could be:
=IIf(Count("*") < 10, Null, Count("*"))
Then set CanShrink to Yes on the text box, as well as the section. If the
text boxes can be collapsed like that instead of by code, you may find that
the pages are formatted correctly.

As you already know, the Format event of the sections results in unreliable
layout, and even inconsistent results. For example, if you preview the first
page and jump to page 8, you may get a different result than if you stepped
through all pages from 1 to 8, because the event procedures for the
intervening pages did not fire.

AFAIK, there is no way to get consistent results if you use the event
procedures.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Actually I am supressing a group total, not a record.

Yes, code in the event procedures is likely to cause these numbering
problems.

The solution is to exclude the records from the report's source query
instead of suppressing them with the events.

My page numbering in my access 2003 report is all goofy. It's showing a
total
of 12 pages but the last page says 13 of 12. There are 13 pages in all.
I
am
using the automatic page numbering [Page] & [Pages]. I am canceling
some
group totaling events based on data meeting a certain criteria for that
level. Is this the cause? How can I work around this?

 

[Guest]

The entries are not supressed, just the totals. I think Access is still
counting the lines as printed, even though they are not printing. If so, is
there a a way to modify this count?

What does AFAIK mean? I see what you mean about using code in events during
formatting.

Is there any way to suppress the entries themselves, instead of suppressing
the section?

For example, if you want to suppress the entry if there are fewer than 10,
the control source could be:
=IIf(Count("*") < 10, Null, Count("*"))
Then set CanShrink to Yes on the text box, as well as the section. If the
text boxes can be collapsed like that instead of by code, you may find that
the pages are formatted correctly.

As you already know, the Format event of the sections results in unreliable
layout, and even inconsistent results. For example, if you preview the first
page and jump to page 8, you may get a different result than if you stepped
through all pages from 1 to 8, because the event procedures for the
intervening pages did not fire.

AFAIK, there is no way to get consistent results if you use the event
procedures.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Actually I am supressing a group total, not a record.

Yes, code in the event procedures is likely to cause these numbering
problems.

The solution is to exclude the records from the report's source query
instead of suppressing them with the events.

My page numbering in my access 2003 report is all goofy. It's showing a
total
of 12 pages but the last page says 13 of 12. There are 13 pages in all.
I
am
using the automatic page numbering [Page] & [Pages]. I am canceling
some
group totaling events based on data meeting a certain criteria for that
level. Is this the cause? How can I work around this?

 

[Allen Browne]

As far a I know, you can find most acronyms here:
http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=AFAIK

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

The entries are not supressed, just the totals. I think Access is still
counting the lines as printed, even though they are not printing. If so,
is
there a a way to modify this count?

What does AFAIK mean? I see what you mean about using code in events
during
formatting.

Is there any way to suppress the entries themselves, instead of
suppressing
the section?

For example, if you want to suppress the entry if there are fewer than
10,
the control source could be:
=IIf(Count("*") < 10, Null, Count("*"))
Then set CanShrink to Yes on the text box, as well as the section. If the
text boxes can be collapsed like that instead of by code, you may find
that
the pages are formatted correctly.

As you already know, the Format event of the sections results in
unreliable
layout, and even inconsistent results. For example, if you preview the
first
page and jump to page 8, you may get a different result than if you
stepped
through all pages from 1 to 8, because the event procedures for the
intervening pages did not fire.

AFAIK, there is no way to get consistent results if you use the event
procedures.

Actually I am supressing a group total, not a record.

:

Yes, code in the event procedures is likely to cause these numbering
problems.

The solution is to exclude the records from the report's source query
instead of suppressing them with the events.

My page numbering in my access 2003 report is all goofy. It's
showing a
total
of 12 pages but the last page says 13 of 12. There are 13 pages in
all.
I
am
using the automatic page numbering [Page] & [Pages]. I am canceling
some
group totaling events based on data meeting a certain criteria for
that
level. Is this the cause? How can I work around this?