This is a multi-part message in MIME format.
--=_NextPart_000_0010_01C4B46D.29F1E490
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I haven't the slightest clue how to go about requesting posts to be = removed.
Can the Moderator for this newsgroup please remove message:
outOVIpsr8sEHA.3912@.TK2MSFTNGP10.phx.gbl
Thanks.
--
Regards,
Tim Ellison, MCP
Ironworks Consulting, LLC
--=_NextPart_000_0010_01C4B46D.29F1E490
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I haven't the slightest clue how to go = about requesting posts to be removed.
Can the Moderator for this newsgroup = please remove message:
outOVIpsr8sEHA.3= 912@.TK2MSFTNGP10.phx.gbl
Thanks.
-- Regards,
Tim Ellison, MCPIronworks Consulting, LLC
--=_NextPart_000_0010_01C4B46D.29F1E490--LOL!
Somebody needs an introductionary course "Newsgroups: how, what, where &
when" :-)
"TIM ELLISON" wrote:
> I haven't the slightest clue how to go about requesting posts to be removed.
> Can the Moderator for this newsgroup please remove message:
> outOVIpsr8sEHA.3912@.TK2MSFTNGP10.phx.gbl
> Thanks.
>
> --
> Regards,
> Tim Ellison, MCP
> Ironworks Consulting, LLC
>
Showing posts with label plain. Show all posts
Showing posts with label plain. Show all posts
Wednesday, March 28, 2012
Friday, March 9, 2012
Missing Row in Excel
All,
We have found a problem with the Excel export today that we cannot
explain at all. We have a plain tabular report that our users
constantly export to Excel.
So far, we haven't had any issues whatsoever, but we have found a very
specific scenario in which the last row doesn't get exported to Excel;
This problem happens only for the Excel export, as all other formats
don't miss the row and the export is 100% sucessful. Bear in mind,
that if we display a different set of results for the same report, the
export is correct. This behaviour is not random, and it can be
repeated time after time.
We would like to know if anybody else as experienced this problem
before, or if there is any known solution.
By the way, we also have seen that when the report doesn't produce any
results at all, that is, only the column headers are displayed, the
export fails with the following error: "Width of excel cell in the
excel sheet exceeded the maximum limit of 1726.5 Points". We know
this problem is documented, but when is it going to be corrected?
Cheers,
Justo.Justo,
I am going to contact you directly about getting a reproduction for the
first issue.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Justo Ruiz" <justoruiz@.hotmail.com> wrote in message
news:d9bb778e.0408200604.5d12c446@.posting.google.com...
> All,
> We have found a problem with the Excel export today that we cannot
> explain at all. We have a plain tabular report that our users
> constantly export to Excel.
> So far, we haven't had any issues whatsoever, but we have found a very
> specific scenario in which the last row doesn't get exported to Excel;
> This problem happens only for the Excel export, as all other formats
> don't miss the row and the export is 100% sucessful. Bear in mind,
> that if we display a different set of results for the same report, the
> export is correct. This behaviour is not random, and it can be
> repeated time after time.
> We would like to know if anybody else as experienced this problem
> before, or if there is any known solution.
> By the way, we also have seen that when the report doesn't produce any
> results at all, that is, only the column headers are displayed, the
> export fails with the following error: "Width of excel cell in the
> excel sheet exceeded the maximum limit of 1726.5 Points". We know
> this problem is documented, but when is it going to be corrected?
> Cheers,
> Justo.|||Bruce/Justo,
Did you resolve this issue? I am experiencing exactly the same
problem...the last row missing only in Excel exports.
Any ideas?
Thanks
TJ
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:%23OqJmTthEHA.704@.TK2MSFTNGP12.phx.gbl...
> Justo,
> I am going to contact you directly about getting a reproduction for the
> first issue.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Justo Ruiz" <justoruiz@.hotmail.com> wrote in message
> news:d9bb778e.0408200604.5d12c446@.posting.google.com...
> > All,
> >
> > We have found a problem with the Excel export today that we cannot
> > explain at all. We have a plain tabular report that our users
> > constantly export to Excel.
> >
> > So far, we haven't had any issues whatsoever, but we have found a very
> > specific scenario in which the last row doesn't get exported to Excel;
> > This problem happens only for the Excel export, as all other formats
> > don't miss the row and the export is 100% sucessful. Bear in mind,
> > that if we display a different set of results for the same report, the
> > export is correct. This behaviour is not random, and it can be
> > repeated time after time.
> >
> > We would like to know if anybody else as experienced this problem
> > before, or if there is any known solution.
> >
> > By the way, we also have seen that when the report doesn't produce any
> > results at all, that is, only the column headers are displayed, the
> > export fails with the following error: "Width of excel cell in the
> > excel sheet exceeded the maximum limit of 1726.5 Points". We know
> > this problem is documented, but when is it going to be corrected?
> >
> > Cheers,
> >
> > Justo.
>
We have found a problem with the Excel export today that we cannot
explain at all. We have a plain tabular report that our users
constantly export to Excel.
So far, we haven't had any issues whatsoever, but we have found a very
specific scenario in which the last row doesn't get exported to Excel;
This problem happens only for the Excel export, as all other formats
don't miss the row and the export is 100% sucessful. Bear in mind,
that if we display a different set of results for the same report, the
export is correct. This behaviour is not random, and it can be
repeated time after time.
We would like to know if anybody else as experienced this problem
before, or if there is any known solution.
By the way, we also have seen that when the report doesn't produce any
results at all, that is, only the column headers are displayed, the
export fails with the following error: "Width of excel cell in the
excel sheet exceeded the maximum limit of 1726.5 Points". We know
this problem is documented, but when is it going to be corrected?
Cheers,
Justo.Justo,
I am going to contact you directly about getting a reproduction for the
first issue.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Justo Ruiz" <justoruiz@.hotmail.com> wrote in message
news:d9bb778e.0408200604.5d12c446@.posting.google.com...
> All,
> We have found a problem with the Excel export today that we cannot
> explain at all. We have a plain tabular report that our users
> constantly export to Excel.
> So far, we haven't had any issues whatsoever, but we have found a very
> specific scenario in which the last row doesn't get exported to Excel;
> This problem happens only for the Excel export, as all other formats
> don't miss the row and the export is 100% sucessful. Bear in mind,
> that if we display a different set of results for the same report, the
> export is correct. This behaviour is not random, and it can be
> repeated time after time.
> We would like to know if anybody else as experienced this problem
> before, or if there is any known solution.
> By the way, we also have seen that when the report doesn't produce any
> results at all, that is, only the column headers are displayed, the
> export fails with the following error: "Width of excel cell in the
> excel sheet exceeded the maximum limit of 1726.5 Points". We know
> this problem is documented, but when is it going to be corrected?
> Cheers,
> Justo.|||Bruce/Justo,
Did you resolve this issue? I am experiencing exactly the same
problem...the last row missing only in Excel exports.
Any ideas?
Thanks
TJ
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:%23OqJmTthEHA.704@.TK2MSFTNGP12.phx.gbl...
> Justo,
> I am going to contact you directly about getting a reproduction for the
> first issue.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Justo Ruiz" <justoruiz@.hotmail.com> wrote in message
> news:d9bb778e.0408200604.5d12c446@.posting.google.com...
> > All,
> >
> > We have found a problem with the Excel export today that we cannot
> > explain at all. We have a plain tabular report that our users
> > constantly export to Excel.
> >
> > So far, we haven't had any issues whatsoever, but we have found a very
> > specific scenario in which the last row doesn't get exported to Excel;
> > This problem happens only for the Excel export, as all other formats
> > don't miss the row and the export is 100% sucessful. Bear in mind,
> > that if we display a different set of results for the same report, the
> > export is correct. This behaviour is not random, and it can be
> > repeated time after time.
> >
> > We would like to know if anybody else as experienced this problem
> > before, or if there is any known solution.
> >
> > By the way, we also have seen that when the report doesn't produce any
> > results at all, that is, only the column headers are displayed, the
> > export fails with the following error: "Width of excel cell in the
> > excel sheet exceeded the maximum limit of 1726.5 Points". We know
> > this problem is documented, but when is it going to be corrected?
> >
> > Cheers,
> >
> > Justo.
>
Subscribe to:
Posts (Atom)