Hi All,

Below is a lengthy overview of a real big problem that we are having. In
short we can not get a PowerBuilder COMPOSITE Datawindow (DW) to print,
using a JAVA resultset as the source of the data. We have provided you with
a detailed explanation of the problem. Any help is VERY MUCH appreciated.

Overview:

We are using PB on the front-end as a ultra-thin client. External
DataWindows are populated by Jaguar(JAVA) resultsets. The PB7 app has no
transaction object associated with it all.

The report below, a parent/child report, is the objective. Cities can have 0
to n entries. The countries are in one resultset and the cities are in
another resultset that can be retrieved based on a countryid.

There is an existing DataWindow that can be used for the country detail line
and another DataWindow that can be used for the city portion of the report.

United Kingdom
London other info about London here
Kingston other info about Kingston here

United States
New York other info about New York here
Chicago other info about Chicago here
Dallas other info about Dallas here

other countries and cities follow
.
.
.

The information below is from the PowerBuilder help file.

>From PB help file.

GetChild()
Provides a reference to a child DataWindow or to a report in a composite
DataWindow, which you can use in DataWindow functions to manipulate that
DataWindow or report.

The keyword in the above statement is the word COMPOSITE. To get a reference
to a child, it has to be in a composite DW. If we can't get a reference to
the DW then we can't populate it from the resultset, or any other way.

====

>From PB help file.

Nested reports and external data sources:
You can't use GetChild to get a reference to a report in a composite
DataWindow when the data source of the nested report is external.

So this eliminates using external DWs. The next step was to create SQL DWs
that are populated from resultsets. The DWs are designed and built using a
connection to Oracle, but would have no database connection at run-time.
Since PB would now not complain about external DWs, this would also let us
keep the 3-tier architecture.

====

Below are some of the things I've tried and why they failed. I don't think
this is rocket science, so what am I missing?

I'm trying to keep the PowerBuilder side of the app from connecting to the
database. All DB connection is done through JAGUAR and returned resultsets.
If there is no other way than to connect to the DB, would someone let me
know?

Scenario 1:
Composite report using nested reports (external DW). Both the country and
city DWs are nested in a composite report.

Can't get a reference to the child (external) DWs.

====

Scenario 2:
Composite report using nested reports (SQL DW)

Allows us to get a reference to the child DWs. The first nested report
prints then the second nested report prints (only for the last row in the
parent report). This would list all of the countries on the first few pages,
then a list of cities on the next page.
I tried printing one country at a time but couldn't get it to work.

====

Scenario 3:
Normal grid/tabular report using Country in the detail band and nested City
DW in the detail band (external DW)

Can't get a reference to the child (external) DW because this is not a
composite DW and it's external as well.

====

Scenario 4:
Normal grid/tabular report using Country in the detail band and nested City
DW in the detail band (SQL DW)

Can't get a reference to the child DW because this is not a composite DW.

====

TIA

Regards,

Rich
____________________________________
Global Trade Management Systems, LLC
e-mail: rmiller@gtmsllc.com