>Thanks, I'll make the changes. Sounds like that will fix it.
>
>By the way, here is a screenshot of the report:
http://www.foxite.com/archives/0000194825.htm >
>Can you help me with the next issue on this report? It is regarding grouping in a multi-detail band report... The screenshot shows my current report that uses only one detail band with a complex "Print When" strategy to make it work.
>
>I currently simulate mutiple bands as a single query containing 3 sets of child records to the main parent. It needs grouping to occur on the second band, based on the Machine_Number of the child records.
>
>When I tried to convert the report to use actual multiple bands, and then added grouping definition, it applies as an outer wrapper to all the detail bands, but I only need it INSIDE of one of the bands.
>
>Do you know of any way to make this work. (See the screenshot for a marked up report to see what I mean)
Hi Mat,
Have look at
www.report-sculptor.comYour report requirement looks like pretty good use-case for my RS, so if you don't mind, I would like to use that layout as
an example for next release of RS. If you send me your data layout (as free tables) I could also send you back RS implementation of your report which you can actually use. FYI report you need is not at all dificult to implement with ReportSculptor.
(Certainly easier then what you went trought to get it to work as FRX)
RS supports high level report scripting where you can use actual form containers as report bands. So you can do that layout you want without using actual frx. You use FORM instead. You stage dataflow/grouping directly in code and then you simply call form containers as report bands. (btw Grouping of records is not that much of rocket science really, you can do as many levels you need)
With RS you get to fully control when each 'band' is going to flash, and each page is going to turn. You get to control everything.
If you are interested experimenting and beta testing RS, I can email you latest yet unpublished version of RS which is much more
easier to implement/integrate. One which is now on website is a bit outdated and is more of a demo/betatest.
So if I got you puzzled drop me an email :)
Sergio
