>>You may be making the same mistake that I keep seeing people make with multiple detail bands. If all you have is one parent record ... and then another table with child records ... you do NOT have a situation for multiple detail bands. What you should be doing is driving the report with the child table and have a relation to the parent table. Create a data group on the field that matches up with the parent. Put all the parent information in the data group header band. Put all the child information in the detail band. No need for a second detail band.
>>
>
>You see, right now, as you suggested, the report can be created without multiple detail bands. But I need to enhance the report and to add another table. Therefore, I will truly have a case for multiple-detail band. Here is what I have and will have:
>1.Main table (Work Order) of one record (actually table has many records, but I need to report on one record only, that's why I use NEXT 1 in the Report form command.
>2.Child table: parts. Related to the Work Order table.
>3.Child table: tasks. Related to the Work Order table.
>Right now, in my initial testing, I only have 1. and 2. But it does not work. I suspect that the cause is NEXT 1. I will test an approach without NEXT 1.
Hi Dmitri
You might want to have look at
www.report-sculptor.com Here is sample that does free report with form containers as bands. I have done this sample besed on thread here (by Matt Slay)
few months ago where he needed 3 band report with grouping applied on band number 2. I enhanced it little bit to do grouping on third band as well. (Original was done by merging data into one cursor and doing print-when)
http://www.report-sculptor.com/community/gallerymenu#GroupingOnMultipleInnerBandsIt is perhaps simillar to where your report might want to go.
Beauty of this 'beast' is that you get to drive report in a freely staged dataflow and flash bands as you are pleased.
You get multple bands driven by you, rather then FRX engine.
Instead of trying to fit your data (by preprocessing,SQL etc) into multiple related cursors to get what you want within
FRX multiband paradigm, you instead drive report directly and create ad-hoc your own multiband reporting structure.
Imagine if you had 'Print/When' clause on inner band in FRX multiband report, would not that be nice ?
Here you get much more then that. You get 'Print-what-and-when-I-tell-you' clause on whole report {g}.
You can do anything you want practically. Report multiple tables (related or unrelated ) , combine container bands with textmerge/boiler plate text, call entire FRX-es to be rendered along etc. (And many more things)
All free / Have look :)
HTH
Sergio
