Confusing Subreport behavior

[Guest]

I have a main report that basically shows a bunch of subreports. None are
linked up to the main report, it is just an area to bring a lot of info
together.

Here is my problem.

Every report works but one. The one report that won't work behaves normally
when opened on it's own. But when brought into the main report, it will only
display a couple of records. Everything is the same as the other reports
(can grow set to Yes, etc). If I stretch out the area for the report more
records will show up. But I can make it .1 inch tall and it will expand out
to show a couple of records, but not the rest.

Every other report will expand from the .1 on the main report out to
whatever it needs.

I've tried copying one of the other reports and changing the subreport
source to the other report and that didn't fix it either.

I don't have a clue what could cause this.

I've also tested this on a different blank report and the report does the
same thing and other reports won't. I'm very confused. I've also re-created
the report from scratch. I'm guessing it is something in the data, but I
don't know.

Nathan

 

[Guest]

Nathan:

Is the subreport multi-columned, and if so are they 'down' then across'
columns? There is a bug associated with the use of that layout as a
subreport. 'Across then down' works fine, however.

Or it may be a problem with the data as you say. Is the report's
RecordSource a query which references some object(s) as a parameter(s)? If
you post the SQL of the underlying RecordSource it may give us a clue.

As the problem report opens fine as a parent report, one solution would be
to use this as the 'container;' for the other subreports, which should work
as the subreports are not linked to any parent report.

Ken Sheridan
Stafford, England

 

[Guest]

Here is the SQL for the "bad" report

SELECT LeeReport_BuildLoss.*, LeeReport_BuildLossArea.LossArea
FROM LeeReport_BuildLoss INNER JOIN LeeReport_BuildLossArea ON
LeeReport_BuildLoss.idxBuildLossArea =
LeeReport_BuildLossArea.idxBuildLossArea
WHERE (((LeeReport_BuildLoss.Id)=[Forms]![BIW_Central]![num]));

Nothing special. The form that it is referencing to is the same thing that
all of the reports reference to. The others don't have a problem with that.

Pulling up the data in query works, and like I said it works on it's own.

I'm gonna try to use this report as the main report now.

Oh, and no there is no column designation. The same basic page layout was
used for each subreport for consistancy. So theoretically I shouldn't have
to write this note, right? What a pain.

Thanks for the help

Nathan

 

[Guest]

Using that bad report as the main report won't work either. I've got data
broken down into individual headers. - Each area having data. So my
detail section would repeat for each. Can I use subreports in the Report
Header?

 

[Guest]

Nathan:

I see no reason why not. And/or in the report footer for that matter, which
would mean you could have some before the detail and some after if necessary.

Ken Sheridan
Stafford, England