Hi everyone,
I have a report where I have a rectangle witha bunch of lists and
textboxes on it which I hide on a certain case. The problem is, its
still taking space on the report page when the report is generated. It
doesn't appear, but I get a big empty space...
Is there any way to let the other items move up a little bit so I don't
have a big gap on my report?
Note: I can't add it to another table since I have lists on the
rectangle...
Thank you,Anyone has any ideas about how to accomplish this by any chance? I am
pretty stuckk...|||Can you try turning "Can Shrink" to true so that when there is no data that
it will shrink to a smaller size and let everything else move up?
"Spartacus" wrote:
> Anyone has any ideas about how to accomplish this by any chance? I am
> pretty stuckk...
>|||If it possible on Image or Rectangle?
Image and Rectangle doesn't have CanShrink.
Any idea?
Thanks!
Angi
"KimB" <KimB@.discussions.microsoft.com> ¼¶¼g©ó¶l¥ó·s»D:7DB5C4A0-0C88-4CE1-99A9-BB5BAE2E0F14@.microsoft.com...
> Can you try turning "Can Shrink" to true so that when there is no data
> that
> it will shrink to a smaller size and let everything else move up?
> "Spartacus" wrote:
>> Anyone has any ideas about how to accomplish this by any chance? I am
>> pretty stuckk...
>>
Showing posts with label bunch. Show all posts
Showing posts with label bunch. Show all posts
Friday, March 23, 2012
hidden field populating header/footer trick not working
I'm a bit stumped at this. I have done this before a bunch of times. The difference is that this time I have two rectangles in the footer. For the each, the visibility is set to an expression which checks whether the page is page 1 or 2. If it is 1, the first rectangle is visible, if 2, the second. When I reference the hidden fields on the main area of the report via ReportItems, they come through fine on the first rectangle, but are invisible on the second. I've tried the same exact fields and every time they are visible in rectangle1, and invisible in rectangle2. What is going on here?
Well, just switched the conditional visibility so that rect1 would go on page 2 and rect2 on page one, and guess what? Now these fields on invisible on rect1 and visible on rect2! So it has to do with the page number! Wow, how weird! Anyone see this before and is there any workaround?
|||
Well, just switched the conditional visibility so that rect1 would go on page 2 and rect2 on page one, and guess what? Now these fields on invisible on rect1 and visible on rect2! So it has to do with the page number! Wow, how weird! Anyone see this before and is there any workaround?
|||
Expressions in the page header/footer can only reference report items on the current page. One thing to check is whether the hidden textbox in the report body is repeated on both pages? If the textbox only appears on the first page, expressions in the header/footer for the second page would always get a null value for this textbox.
sqlhidden field populating header/footer trick not working
I'm a bit stumped at this. I have done this before a bunch of times. The difference is that this time I have two rectangles in the footer. For the each, the visibility is set to an expression which checks whether the page is page 1 or 2. If it is 1, the first rectangle is visible, if 2, the second. When I reference the hidden fields on the main area of the report via ReportItems, they come through fine on the first rectangle, but are invisible on the second. I've tried the same exact fields and every time they are visible in rectangle1, and invisible in rectangle2. What is going on here?
Well, just switched the conditional visibility so that rect1 would go on page 2 and rect2 on page one, and guess what? Now these fields on invisible on rect1 and visible on rect2! So it has to do with the page number! Wow, how weird! Anyone see this before and is there any workaround?
|||
Well, just switched the conditional visibility so that rect1 would go on page 2 and rect2 on page one, and guess what? Now these fields on invisible on rect1 and visible on rect2! So it has to do with the page number! Wow, how weird! Anyone see this before and is there any workaround?
|||
Expressions in the page header/footer can only reference report items on the current page. One thing to check is whether the hidden textbox in the report body is repeated on both pages? If the textbox only appears on the first page, expressions in the header/footer for the second page would always get a null value for this textbox.
Subscribe to:
Posts (Atom)