Well I take that back - there's no region there. (Helps if I look at the right report.)
But a line is definitely not a region, so my guess is when the report was designed, it was determined that the subreport would not grow beyond the limits of the line object, so the region is not needed. Dawn Hast [EMAIL PROTECTED] wrote on 06/04/2008 04:44:10 PM: > > Well, I'm certainly not the person to speak to your perceptions, but > it looks to me like there's a line and a region. The line is white > and set to parent height and parent width. Why is it there? I've > got no idea. But in my copy, there is also a region in the detail > section. My guess is your region is hiding behind your line object. > Send it to the back. > > Dawn > > > > > > "Wills, Steve" <[EMAIL PROTECTED]> wrote on 06/04/2008 04:35:17 PM: > > > Just having taken a look at the help-docs on SubReports and the example > > reports described therein, I came across an implementation technique > > that triggered my curiosity. Whereas, in the Detail band in which I > > expected to find a Region, I found that the "region" was actually a Line > > Object, I am forced to ask, "Why and how does a Line Object become what > > I perceive to be a functional equivalent for a Region?" > > > > Are the particular/peculiar circumstances where this is the better way > > to skin the cat? > > > > (PS - I'm not anti-feline, but y'all know what I mean.) > > > > Thanks, > > Steve in Memphis > > > > > > > > J. Stephen Wills > > Program Manager, Research Informatics > > Office of the Vice Chancellor for Research > > University of Tennessee Health Science Center > > 62 S. Dunlap, Suite 400 > > Memphis, TN 38163 > > Office: 901-448-2389 > > FAX : 901-448-7133 > > > >
