Jump to content
We've recently updated our Privacy Statement, available here ×

SubReport not working.....


Go to solution Solved by narcism,

Recommended Posts

Hi Folks:

I've done several generic reports in the past, but have never used a SubReport before now.  I've tried to watch a few videos and also read through several articles here/elsewhere, but I'm missing something.

I created a very short video to show what I have done and what the issue is:

If any one can help me I would appreciate it  very, very much.

I also have some screen pics below....

The Main Oracle Report is based off of a view which is working fine:

http://cwebpro.com/SQL/SQL_MAIN_REPORT.PNG

The SubReport is based off of a different view:

http://cwebpro.com/SQL/SQL_FOR_SUBREPORT.PNG

The two reports are linked through: ANIMAL,EXAM_DATE,DIAGNOSTICIAN, and DIAGNOSIS (If this were a table, that would be the compound PK).

The ERROR:   When I run the report (click on Preview in studio) it tries to give me like 60000 pages (should be about 50).

Below are some screen pics of some settings that can give you more information:

Subreport Query with Parameters

http://cwebpro.com/SQL/SQL_AND_PARAMETERS_FOR_SUBREPORT.PNG

Location SubReport:
http://cwebpro.com/SQL/SUBREPORT_IN_MAIN_REPORT.PNG

SubReport Parameters:

http://cwebpro.com/SQL/SUBREPORT_PARAMETERS.PNG

Parameters in Outline View:

http://cwebpro.com/SQL/SUBREPORT_PARAMETERS_InOutline.PNG

Thank you for your help Folks!

Matthew

Link to comment
Share on other sites

  • Replies 5
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

  • Solution

A couple of things to check, each at a time:

1. Make sure you recompile your subreport every time you modify it. You may have an old *.jasper file for it and that one gets picked up by your mainReport.

2. Place some limits on the mainReport's query and check the data from the subreport. You could even place some textfields with your parameters at the top of the subreport, in a title band for instance, to see if they get passed correctly.

3. Perform some record counting to understand how big the resultsets are, especially for the subReport's query.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...