Can anyone shed any light on why this behaviour may be occurring and suggest how it can be overcome so that the child data can be displayed in the grid.
Hi,
Thank you for your email. I'm currently out of the office for business. I will return on December 6. During my absence I will have no or very limited access to my email. For urgent matters, call me on my mobile and leave a message on my voice mail or call our office.
Best regards,
Wouter.
--
Wouter Dupré
Senior Solution Consultant
Progress Software NV
Stocletlaan 202 B| B-2570 Duffel | Belgium
Office +32 (0) 15 30 77 00 | Mobile +32 (0) 478 50 00 49 wdupre@progress.com
Can anyone shed any light on why this behaviour may be occurring and suggest
how it can be overcome so that the child data can be displayed in the grid.
You may need to reopen the parent query. Is the GetChildDataForThisRecord() call returning parent records too?
-- peter
Hi Peter,
sorry for the delay have had problems loggin in to the communities pages.
to answer your question
No the GetChildDataForThisRecord() call does not return parent data.
What the application is doing is returning a list of available products, some of which have special offers.
clicking on the [+] to expand the (special offer) child rows is being trapped by the "BeforeRowExpanded" event
at this point the call is made to get related special offers (if there are any). The data set is being passed as an input-output parameter.
Outputing the product and special offers temp-tables shows the only change was to add rows for the special offers temp-table.
I tried re-opening the parent query but that did not work.
One thing I failed to mention was that on returning to the BeforeRowExpanded event we are executing a
bindingsource2:RefreshAll().
The concept we were trying to get working was to avoid returning all of the Special Offers at the same time.
The application would return the special offers for the products the users are interested in.
For now we are returning all of the special offers with the products.