Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems with Nested Report

Status
Not open for further replies.

PowerbuilderAngel

Programmer
Jan 8, 2003
3
US
Good website!
I have 2 questions, I am using Powerbuilder 7.0 in Windows 2000 environment.

Problem 1: I have a nested report where the main report is type grid and the nested report is type freeform.
When I run this report in development mode, it runs, when I run the application the report does not show the nested report at all. What is the problem?

Problem 2: With the same report, after I send the report to the printer, a blank page prints after each page with data. What is the problem?


Thanks
for your help
 
I have found that when I use nested reports within a datawindow, I need to ensure that there are no fields on the nested datawindow that are not visible on the parent datawindow. i.e, I use nested reports within a report for displaying many-to-one relationships such as client attributes. The source for my nested report contained both an attribute code and an attribute description. I had the nested source datawindow sized to only show the attribute description with the attribute code off to the right side out of view. I likewise sized the nested report on the parent datawindow to fit the attribute description. Printing resulted in the same blank pages you are experiencing. I finally deleted the attribute code from the source datawindow to solve the problem.
 
Thanks for your quick reply. I am so sorry but I do not understand what you mean by the nested report containing
an attribute code and an attribute description. I just have an sql statement in the nested report.
 
PowerBuilderAngel,
Sorry for the confusion. The nested report I used consisted of a datawindow with two columns of data, a client attribute code and a associated attribute definition as the report source (i.e. code 100 = English). Even though only the attribute definition was visible in the source datawindow and the nested report was sized to match, the printed report printed a blank page. I found when I removed the source datawindow column that was out of view in the source datawindow that the nested report then worked properly without printing the blank page. I have not used nested reports with only a SQL statement however I would expect the results to be the same. Are you certain that the display width of your nested report is wide enough to contain all of the fields/columns in your SQL query?

Don Ely
don_ely@earthlink.net
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top