GetChild for a nested report in a freeform

[Juan Jara]

Hello

How can I get child for a nested report in a freeform datawindow?. When I
call getchild It returns -1.
Thank you in advance.

[Juan Jara]

With freeform datawindows it doesn't work, is it?.
How can I get the retrieval arguments in a composite datawindow? Because I
need them to retrieve the nested reports.

<Mike> escribió en el mensaje
news:8A5BF559C218E8C1003A616F85256B0D.0033CFEC85256B0D@webforums...
> From help file:
> >> A report is a DataWindow that is part of a composite DataWindow. A
> report is read-only. When you define the composite DataWindow in the
> DataWindow painter, each report is given a name. You can see the name in
> the Name option of the Properties view. You must use the report name (not
> the name of the DataWindow object in which the report has been placed)
when
> calling GetChild. <<
>
> Are you definitely using the report name and not the datawindow name? Is
> it a composite datawindow?
>
> Mike

[Mike]

[Frederic Hoornaert]

I have had the same problem as you, i have been looking around a bit in the
PowerBuilder Tips&Tricks, and i have found the solution :
1. You have to export you Freeform datawindow into a SRD file.
2. In the SRD file, you will find something like PROCESSING=0
(tabular/freeform) or PROCESSING = 1 (grid)
3. Replace this by PROCESSING=5 (which makes it a composite) , and import
the file again.
4. No you should be able to get the datawindow child using the report name
you gave it. (The name of the nested report, not the name of the datawindow
!!)

Remark: You will not be able to return to SQL syntax in powerbuilder when
you have converted the freeform into a composite. If you need to modify the
SQL of the datawindow, then you will have to do the contrary, (export, put
processing = 1, import, modify SQL, export, modify processing to 5 again,
import again).
I hope it works for you, because for us it worked ...

Frederic

Juan Jara <jj...@nikel.es> a écrit dans le message :
lFeJ0LB...@forums.sybase.com...

[Bug]

AFAIK, nested reports get their retrieval arguments from the parent dw. Try
defining the arguments in the outer dw and see if that helps your retrieve
on the nested ones.

"Juan Jara" <jj...@nikel.es> wrote in message
news:lFeJ0LB...@forums.sybase.com...