Revisiting - Stymied by report hang in Access 2000 (A2K) (02/20/2009)

[Larry Kahm]

To recap:

I did make a little progress with this problem after some additional
Googling.

One recommendation, from back in 2005, suggested removing the "of [Pages]"
from the report. I tried that, which actually got past the "Formatting
Report, press CTRL+Break" message.

However, the report only got up to about page 20 whereupon each page
thereafter had only the header with a blank page - and it went on from there
to infinity.

I am open to any - and all - suggestions as to how to get this fixed.

Thanks!

Larry

 

[Paul Shapiro]

If you don't have any better ideas, I would make experiment with a copy of
the database. Either remove elements one at a time until it works, or start
with just the parent report, removing all subreports. If that works, add the
first level supreport, but with the sub-sub grandchild report removed. Etc.
Once you get down to the smallest unit that makes a difference, it can help
focus your investigation. Then try removing controls, code, etc. until you
find the source of the problem.

How big is the report? If it's 100's of pages, then any reference to [pages]
requires the entire report to be formatted before the first page can be
displayed. If you have a clue that without that the first 20 pages are ok,
and then the problem happens, look at the data that's appearing on page
20-21 or so to see if the data has an impact.

To recap:

I did make a little progress with this problem after some additional
Googling.

One recommendation, from back in 2005, suggested removing the "of [Pages]"
from the report. I tried that, which actually got past the "Formatting
Report, press CTRL+Break" message.

However, the report only got up to about page 20 whereupon each page
thereafter had only the header with a blank page - and it went on from
there to infinity.

I am open to any - and all - suggestions as to how to get this fixed.

 

[Larry Kahm]

Paul,

Thanks for the reply. The report - when I run it in the test environment -
is about 35 pages.

I've looked at the record that's causing the problem on page 20. In fact, I
ran the report and filtered it for just that one record - and it was fine!

Later this week I'll have an opportunity to selectively reduce the fields
and controls and see what happens.

If anyone else has any suggestions, I'm more than willing to listen.

Larry

If you don't have any better ideas, I would make experiment with a copy of
the database. Either remove elements one at a time until it works, or
start with just the parent report, removing all subreports. If that works,
add the first level supreport, but with the sub-sub grandchild report
removed. Etc. Once you get down to the smallest unit that makes a
difference, it can help focus your investigation. Then try removing
controls, code, etc. until you find the source of the problem.

How big is the report? If it's 100's of pages, then any reference to
[pages] requires the entire report to be formatted before the first page
can be displayed. If you have a clue that without that the first 20 pages
are ok, and then the problem happens, look at the data that's appearing on
page 20-21 or so to see if the data has an impact.

To recap:

Main report has one sub-report that has one sub-report (parent, child,
grandchild).
Reort produces results in single development MDB
Report produces results in test environment when split between BE on
server and FE on local machine using customer data in the BE
Report hangs in production environment when using split BE/FE
irrespective of the FE being an MDB or MDE.

I did make a little progress with this problem after some additional
Googling.

One recommendation, from back in 2005, suggested removing the "of
[Pages]" from the report. I tried that, which actually got past the
"Formatting Report, press CTRL+Break" message.

However, the report only got up to about page 20 whereupon each page
thereafter had only the header with a blank page - and it went on from
there to infinity.

I am open to any - and all - suggestions as to how to get this fixed.

 

[Larry Kahm]

Correction, when I ran the report and set the filter for the mis-behaving
record, it did >not< produce the complete report. I could have sworn it
did, but I was wrong.

The solution - after much trial and error - was to set the detail section's
KeepTogether property (in the first nested sub-report) to No! And to make
sure that the respective CanGrow/CanShrink properties in all of the reports
were set to Yes.

Perseverance - it seems to be a very good word these days.


Larry

Paul,

Thanks for the reply. The report - when I run it in the test
environment - is about 35 pages.

I've looked at the record that's causing the problem on page 20. In fact,
I ran the report and filtered it for just that one record - and it was
fine!

Later this week I'll have an opportunity to selectively reduce the fields
and controls and see what happens.

If anyone else has any suggestions, I'm more than willing to listen.

Larry

If you don't have any better ideas, I would make experiment with a copy
of the database. Either remove elements one at a time until it works, or
start with just the parent report, removing all subreports. If that
works, add the first level supreport, but with the sub-sub grandchild
report removed. Etc. Once you get down to the smallest unit that makes a
difference, it can help focus your investigation. Then try removing
controls, code, etc. until you find the source of the problem.

How big is the report? If it's 100's of pages, then any reference to
[pages] requires the entire report to be formatted before the first page
can be displayed. If you have a clue that without that the first 20 pages
are ok, and then the problem happens, look at the data that's appearing
on page 20-21 or so to see if the data has an impact.

To recap:

Main report has one sub-report that has one sub-report (parent, child,
grandchild).
Reort produces results in single development MDB
Report produces results in test environment when split between BE on
server and FE on local machine using customer data in the BE
Report hangs in production environment when using split BE/FE
irrespective of the FE being an MDB or MDE.

I did make a little progress with this problem after some additional
Googling.

One recommendation, from back in 2005, suggested removing the "of
[Pages]" from the report. I tried that, which actually got past the
"Formatting Report, press CTRL+Break" message.

However, the report only got up to about page 20 whereupon each page
thereafter had only the header with a blank page - and it went on from
there to infinity.

I am open to any - and all - suggestions as to how to get this fixed.