Report Hanging Up

This is my first post here. Looks like you've got a pretty active group so here goes...

I have a report that hangs up at the "Formatting Page" prompt. I can hit "ctrl/break" and stop everything, but I obviously need the report to work properly.

I've got one subreport on it. When I remove the subrpt, everything works fine. The subreport runs ok when I open it on it's own and I can't identify any problems with null data or master/child linking.

Any ideas?

Where have you put the subreport in the main form?

Detail section, far right side. The subreport has multiple "notes" related to each unit in the detail. There is grouping in sorting on the main report, but removing the groups and sorts has no effect.

One more thing: My grouping is based on a concatenated field of Region & Unit Status. There are only two combinations that are causing me problems. If I filter out those two combinations, the report (including the sub) runs fine. All other combinations of Region & Unit status work fine - including other statuses from the same region, and the same statuses from other regions.

I have checked and experimented with the data that the subreport is supposed to show for this particular Region/Status combination and there is nothing unusual.

In all of the hundreds and hundreds of complex Access reports I've created over the past several years, I've never come across this problem and I can't find anything on it in the knowledge base.

Have you got your master/child links correct. Do you have the concatenated field as the link field?

yes, the report & subreport work fine for all region/status combinations except for these two, so the master/child relationships are ok.

no, the concatenated field is not involved in the link at all. I tinkered around with the concatenation and with the grouping, and there was no effect. All region/status combinations worked fine w/o the subreport and all but two region/status combinations worked with the subreport.

I think that there's just something in the subreport's source table that's causing a problem. When I return to the client tomorrow, I'm going to browse through the records in that table for any unusual characters. If I don't find anything there, I'm going to start running the report one record at a time to see if I can isolate which records are causing the problem and then investigate further.

In the meantime, please keep the suggestions coming...

Problem found!

The problem was being caused by units that had enough records in the subreport to force the subreport across more than one page. However, I had the detail section in both reports set to "Keep together".

In effect, the main report didn't want to allow page spanning, but the subreport had so many records that it needed to span pages...