Why is it when I export a series of textboxes, all of which have the same
height and top, and each one whose left position is exactly equal to the
left position plus the width of the textbox to the left, they do not export
to a single row in Excel? And not just that, but they'll be *half* a row
off, such that one textbox may span Excel rows 10 and 11, while its neighbor
is on rows 11 and 12? Grids seem to handle this ok, but when you want
something as simple as putting a row of textboxes in the page header to line
up above values in the grid, it makes managers very unhappy when they get
their spreadsheet and the headers are not in a straight line.I should add that TIFF and PDF turns out beautifully, and Web Archive is a
little screwy, but not nearly as bad.
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:OYc4vq1TFHA.3152@.TK2MSFTNGP12.phx.gbl...
> Why is it when I export a series of textboxes, all of which have the same
> height and top, and each one whose left position is exactly equal to the
> left position plus the width of the textbox to the left, they do not
> export to a single row in Excel? And not just that, but they'll be *half*
> a row off, such that one textbox may span Excel rows 10 and 11, while its
> neighbor is on rows 11 and 12? Grids seem to handle this ok, but when you
> want something as simple as putting a row of textboxes in the page header
> to line up above values in the grid, it makes managers very unhappy when
> they get their spreadsheet and the headers are not in a straight line.
>|||I have the same problem :|||I think the problem is the report-head-line's width, try to modify it to the
same as the first column or the same as total clumns.
"DJM" wrote:
> Why is it when I export a series of textboxes, all of which have the same
> height and top, and each one whose left position is exactly equal to the
> left position plus the width of the textbox to the left, they do not export
> to a single row in Excel? And not just that, but they'll be *half* a row
> off, such that one textbox may span Excel rows 10 and 11, while its neighbor
> is on rows 11 and 12? Grids seem to handle this ok, but when you want
> something as simple as putting a row of textboxes in the page header to line
> up above values in the grid, it makes managers very unhappy when they get
> their spreadsheet and the headers are not in a straight line.
>
>|||When I design a report for Excel I do the following. I add an extra table
header row (or multiple). Then you can merge cells appropriately, do any
left/right/center lining up and have what I would normally use textboxes
for. This should get around your problem but more importantly it prevents
the issue where the excel created has the cells created such that you can
still sort appropriately. If you have textboxes above your table then you
can end up with Excel sheet where you cannot sort.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Eric Wang" <Eric Wang@.discussions.microsoft.com> wrote in message
news:8BB5219A-DD84-4308-B99A-1602FC6662E8@.microsoft.com...
>I think the problem is the report-head-line's width, try to modify it to
>the
> same as the first column or the same as total clumns.
> "DJM" wrote:
>> Why is it when I export a series of textboxes, all of which have the same
>> height and top, and each one whose left position is exactly equal to the
>> left position plus the width of the textbox to the left, they do not
>> export
>> to a single row in Excel? And not just that, but they'll be *half* a row
>> off, such that one textbox may span Excel rows 10 and 11, while its
>> neighbor
>> is on rows 11 and 12? Grids seem to handle this ok, but when you want
>> something as simple as putting a row of textboxes in the page header to
>> line
>> up above values in the grid, it makes managers very unhappy when they get
>> their spreadsheet and the headers are not in a straight line.
>>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment