Showing posts with label asking. Show all posts
Showing posts with label asking. Show all posts

Sunday, February 26, 2012

Export to Excel 2007

Hello Everyone,

Is there any way in RS2005 to export to Excel 2007 format ?

The reason I'm asking is that we have a report that can potentially have more than 256 columns but for now, there is no way of directly importing to excel 2003 (.xls).

Is microsoft going to come out with an improvement to RS2005 or is there already a way to export to Excel 2007 to bypass the 256 column limit?

Regards,

Joseph

Reporting Services 2008 should have this functionality I would think.

In the meantime, you could try to use Softartisians OfficeWriter for your issue.

cheers,

Andrew

Friday, February 24, 2012

export to excel

Had anyone made an export to excel that has 33 rows?
33 rows in excel, together with header and all...
I'm asking that because in my case when export to excel has 33 rows, 33.
row is always missing!Do you have SP2 installed? I know it had some Excel export fixes.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jo?ko ?ugar" <josko_bla@.netgen_rem0ve_this_and_bla.hr> wrote in message
news:d83nqc$3ll$1@.sunce.iskon.hr...
> Had anyone made an export to excel that has 33 rows?
> 33 rows in excel, together with header and all...
> I'm asking that because in my case when export to excel has 33 rows, 33.
> row is always missing!|||Bruce L-C [MVP] wrote:
> Do you have SP2 installed? I know it had some Excel export fixes.
>
I do now, but the problem is still there.|||Try adding a blank/empty textbox below your table or matrix. I've seen
cases like this where the last row of a report is missing when exported
to Excel...adding a small, empty textbox immediately below your table
or matrix seemed to fix the problem.|||kbr wrote:
> Try adding a blank/empty textbox below your table or matrix. I've seen
> cases like this where the last row of a report is missing when exported
> to Excel...adding a small, empty textbox immediately below your table
> or matrix seemed to fix the problem.
>
Thanks!