Extra Page in Adobe Export

Using SRS SP2 and Adobe 7.0.2
When my report renders in the preview pane it it limited to one page but
when exported to Adobe it prints an extra page. The report has Page
Header/Body/Page Footer sections.
Is this a bug or am I missing something in the config?
ThanksI have the same problem. Would like to know if there is a solution.
"Mike Harbinger" wrote:
> Using SRS SP2 and Adobe 7.0.2
> When my report renders in the preview pane it it limited to one page but
> when exported to Adobe it prints an extra page. The report has Page
> Header/Body/Page Footer sections.
> Is this a bug or am I missing something in the config?
> Thanks
>
>|||make sure there is no extra space after the table and chart
"Mike Harbinger" wrote:
> Using SRS SP2 and Adobe 7.0.2
> When my report renders in the preview pane it it limited to one page but
> when exported to Adobe it prints an extra page. The report has Page
> Header/Body/Page Footer sections.
> Is this a bug or am I missing something in the config?
> Thanks
>
>|||That was it! I had moved a field in from the right margin and after
tightening it up the extra page was gone.
Many thanks!
"RP" <RP@.discussions.microsoft.com> wrote in message
news:94E1BCC1-F540-46DE-95F7-56F242097113@.microsoft.com...
> make sure there is no extra space after the table and chart
> "Mike Harbinger" wrote:
>> Using SRS SP2 and Adobe 7.0.2
>> When my report renders in the preview pane it it limited to one page but
>> when exported to Adobe it prints an extra page. The report has Page
>> Header/Body/Page Footer sections.
>> Is this a bug or am I missing something in the config?
>> Thanks
>>

extra blank pages when exported to pdf

anyone know why I'm getting an extra blank page after every page when I
export to PDF?I did notice something weird ... I click on the body of the report and try
to change the width 11(w) x 8.5 (h) (landscape report) and it always changes
back to 11.125. I can't get it to change. any ideas?
btw, thank you for the quick reply. I am in a rush for this.
"Mike Collins" <MikeCollins@.discussions.microsoft.com> wrote in message
news:F73E92CC-0FBD-47CE-A284-554CE8FE5118@.microsoft.com...
> Course, I did not answer your question...directly. You are getting blank
> pages because something on your report (report width, a long field) is
> causing this and you are not seeing it by looking at the preview tab.
> "Emil" wrote:
> > anyone know why I'm getting an extra blank page after every page when I
> > export to PDF?
> >
> >
> >|||Please make sure that your report is setup as follows:
(Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=Body.Width
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Emil" <laserview@.hotmail.com> wrote in message
news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> anyone know why I'm getting an extra blank page after every page when I
> export to PDF?
>|||I can't change my body width
(Report.PageWidth - Report.LeftMargin - Report.Right Margin) >= Body.Width
11-.25-.25 = 10.5
Body.width = 11.125
No mater what I do I can't change the body width. Always goes back to 11.125
Any ideas?
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:%23XvlCquhEHA.2340@.TK2MSFTNGP11.phx.gbl...
> Please make sure that your report is setup as follows:
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> Body.Width
>
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Emil" <laserview@.hotmail.com> wrote in message
> news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> > anyone know why I'm getting an extra blank page after every page when I
> > export to PDF?
> >
> >
>|||Make sure u have all the size of reportitems to the <= body width u want.If u
are not able to change the body size means these is
something(textbox,rectangle table etc...)that has width larger that the width
of the body u are trying to set....
blank pages are usually when the following is not true....for the width
Report.PageWidth >= Report.LeftMargin + Report.Right Margin + Body.Width
I hope this helps...
"Emil" wrote:
> I can't change my body width
>
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >= Body.Width
> 11-.25-.25 = 10.5
> Body.width = 11.125
> No mater what I do I can't change the body width. Always goes back to 11.125
> Any ideas?
>
>
> "Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
> news:%23XvlCquhEHA.2340@.TK2MSFTNGP11.phx.gbl...
> > Please make sure that your report is setup as follows:
> >
> > (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> > Body.Width
> >
> >
> > --
> > Bruce Johnson [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Emil" <laserview@.hotmail.com> wrote in message
> > news:e4r37RuhEHA.3016@.tk2msftngp13.phx.gbl...
> > > anyone know why I'm getting an extra blank page after every page when I
> > > export to PDF?
> > >
> > >
> >
> >
>
>|||I have a similiar problem - blank pages being generated when exporting
to PDF. However, I have checked my body(9.9in) vs report page width
(11in) with .25 inch left and rt margins. I think the problem is
related the way RS computes the vertical requirements of outputting a
report -- I have many conditionally hidden lines in a table group. If
I set the List height (4in) just large enough to contain the table, I
only get one page rendered when in fact two pages should be rendered to
PDF. However, if I increse the List height to (4.1in) I generate a
report of 4 pages for what should be a 2-page report with pages 2 and 4
blank.
Does anyone else have this same issue?
Dennis|||I am having the same problem - see below "DD" posting. Have you found
a solution to your problem?|||I was having the same problem (exports to PDF fine from VS IDE, but get extra
pages when I export to PDF from Report Manager). I was able to remedy the
problem by installing service pack 1 for sql reporting services.
"DD" wrote:
> I am having the same problem - see below "DD" posting. Have you found
> a solution to your problem?
>|||I was having the same problem, my fix was strange. In my report I have
detailed lines in which I wanted spaces to separate each row, to do this i
added an extra 2 detailed lines with no data fields on them, there height was
0.3cm, when I removed these emtpy lines or increased the height to 0.5cm the
problem went away.
"Jonathan Gordon" wrote:
> I was having the same problem (exports to PDF fine from VS IDE, but get extra
> pages when I export to PDF from Report Manager). I was able to remedy the
> problem by installing service pack 1 for sql reporting services.
>
>
> "DD" wrote:
> > I am having the same problem - see below "DD" posting. Have you found
> > a solution to your problem?
> >
> >sql

External SQL functions exported by DLLs

We have a few rather advanced calculation routines
developed in C++. Currently we are using a Sybase ASA
database for our app. and these routines are accessible
by so called external functions exported by a DLL
(dynamic link library) that we wrote in C++. Sybase
supports this quite nicely.
The client app can call such routines by:
"select get_roof_angle() as angle from dummy;"
or
":angle = call get_roof_angle();"
Now we are checking if other databases can provide us
with similar abilities. So I just wonder if SQLServer/MSDE
supports the ability to call a routine exported by a
DLL? If yes, does anyone know the SQL syntax to declare
it in SQLServer/MSDE
Best regards
Peter Sullvan
hi Peter,
Peter Sullvan wrote:
> We have a few rather advanced calculation routines
> developed in C++. Currently we are using a Sybase ASA
> database for our app. and these routines are accessible
> by so called external functions exported by a DLL
> (dynamic link library) that we wrote in C++. Sybase
> supports this quite nicely.
> The client app can call such routines by:
> "select get_roof_angle() as angle from dummy;"
> or
> ":angle = call get_roof_angle();"
> Now we are checking if other databases can provide us
> with similar abilities. So I just wonder if SQLServer/MSDE
> supports the ability to call a routine exported by a
> DLL? If yes, does anyone know the SQL syntax to declare
> it in SQLServer/MSDE
> Best regards
> Peter Sullvan
you can write so called "extended stored procedures" externded by dll... at
http://www.sqldev.net/xp.htm you can find some examples as long as usefull
links..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

External SQL functions exported by DLLs

We have a few rather advanced calculation routines
developed in C++. Currently we are using a Sybase ASA
database for our app. and these routines are accessible
by so called external functions exported by a DLL
(dynamic link library) that we wrote in C++. Sybase
supports this quite nicely.
The client app can call such routines by:
"select get_roof_angle() as angle from dummy;"
or
":angle = call get_roof_angle();"
Now we are checking if other databases can provide us
with similar abilities. So I just wonder if MS-SQLServer
supports the ability to call a routine exported by a
DLL? If yes, does anyone know the SQL syntax to declare
it in MS-SQLServer.
Best regards
Peter SullvanCurrently only as (extended) stored procedures.
EXEC xp_procname -- which really is a function in a DLL file.
SQL Server 2005 will implement CLR inside SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Peter Sullvan" <ps@.NOSPAMonline.de> wrote in message
news:%23Usr70jJFHA.3960@.TK2MSFTNGP09.phx.gbl...
> We have a few rather advanced calculation routines
> developed in C++. Currently we are using a Sybase ASA
> database for our app. and these routines are accessible
> by so called external functions exported by a DLL
> (dynamic link library) that we wrote in C++. Sybase
> supports this quite nicely.
> The client app can call such routines by:
> "select get_roof_angle() as angle from dummy;"
> or
> ":angle = call get_roof_angle();"
> Now we are checking if other databases can provide us
> with similar abilities. So I just wonder if MS-SQLServer
> supports the ability to call a routine exported by a
> DLL? If yes, does anyone know the SQL syntax to declare
> it in MS-SQLServer.
> Best regards
> Peter Sullvan
>|||In SQL Server 2000, you can create an extended stored procedure. See the
Books Online for details. For scalar functions, you can encapsulate an
extended stored procedure in a Transact-SQL scalar function like the example
below.
CREATE FUNCTION get_roof_angle()
RETURNS int
AS
BEGIN
DECLARE @.RoofAngle int
EXEC master..xp_get_roof_angle @.RoofAngle OUT
RETURN @.RoofAngle
END
GO
SELECT dbo.get_roof_angle()
GO
The planned SQL Server 2005 version will allow you to develop functions
using CLR managed code.
Hope this helps.
Dan Guzman
SQL Server MVP
"Peter Sullvan" <ps@.NOSPAMonline.de> wrote in message
news:%23Usr70jJFHA.3960@.TK2MSFTNGP09.phx.gbl...
> We have a few rather advanced calculation routines
> developed in C++. Currently we are using a Sybase ASA
> database for our app. and these routines are accessible
> by so called external functions exported by a DLL
> (dynamic link library) that we wrote in C++. Sybase
> supports this quite nicely.
> The client app can call such routines by:
> "select get_roof_angle() as angle from dummy;"
> or
> ":angle = call get_roof_angle();"
> Now we are checking if other databases can provide us
> with similar abilities. So I just wonder if MS-SQLServer
> supports the ability to call a routine exported by a
> DLL? If yes, does anyone know the SQL syntax to declare
> it in MS-SQLServer.
> Best regards
> Peter Sullvan
>|||To clarify my response, you can create extended stored procedures in all
versions of SQL Server. However, Transact-SQL functions are available only
in SQL 2000+.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:%23YTFuOkJFHA.1280@.TK2MSFTNGP09.phx.gbl...
> In SQL Server 2000, you can create an extended stored procedure. See the
> Books Online for details. For scalar functions, you can encapsulate an
> extended stored procedure in a Transact-SQL scalar function like the
> example below.
> CREATE FUNCTION get_roof_angle()
> RETURNS int
> AS
> BEGIN
> DECLARE @.RoofAngle int
> EXEC master..xp_get_roof_angle @.RoofAngle OUT
> RETURN @.RoofAngle
> END
> GO
> SELECT dbo.get_roof_angle()
> GO
> The planned SQL Server 2005 version will allow you to develop functions
> using CLR managed code.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Peter Sullvan" <ps@.NOSPAMonline.de> wrote in message
> news:%23Usr70jJFHA.3960@.TK2MSFTNGP09.phx.gbl...
>|||SQL Server only supports Extended Stored Procedures, no Extended Functions,
but you could wrap an extended stored procedure inside a user defined T-SQL
function and get the same behavior, but you need to use output parameters in
your extended stored procedure to return values, you can not return a result
set.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Peter Sullvan" <ps@.NOSPAMonline.de> wrote in message
news:%23Usr70jJFHA.3960@.TK2MSFTNGP09.phx.gbl...
> We have a few rather advanced calculation routines
> developed in C++. Currently we are using a Sybase ASA
> database for our app. and these routines are accessible
> by so called external functions exported by a DLL
> (dynamic link library) that we wrote in C++. Sybase
> supports this quite nicely.
> The client app can call such routines by:
> "select get_roof_angle() as angle from dummy;"
> or
> ":angle = call get_roof_angle();"
> Now we are checking if other databases can provide us
> with similar abilities. So I just wonder if MS-SQLServer
> supports the ability to call a routine exported by a
> DLL? If yes, does anyone know the SQL syntax to declare
> it in MS-SQLServer.
> Best regards
> Peter Sullvan
>

Exports to Excel the details of the report but I need summary

The trouble I am having is that I have a drilldown report that exports the detail to Excel, but I want the summary exported to Excel.

I perform the following steps but get wrong results. Please help me identify the correct steps for the correct results. Thanks you.

1) Select Matrix.

2) Right click, select Properties.

3) Select tab Groups.

4) Select item in Columns list, click Edit.

5) Select tab Visibility.

6) Select Initial visibility: Hidden, and click okay to the Grouping and Sorting dialog box.

Now I can export summary to Excel okay, but now I can not expand the summary in the report itself, so I do the following:

7) Do one through six above (but do not close dialog box), then click visibility can be toggled by another report item.

8) Select the report item in the Report Item drop down list.

Now the report functions normally in the Reporting Services report web page, but when I export on the summary level, again it exports the detail to Excel, but what I want it to export is the summary.

Ideas?

Is this forum active? Only when the drilldown functionality is disabled does the summary export to excel, even though the summary column is calculated from the underlying detail columns. As soon as the drilldown feature is enabled, then the export to excel generates the detail data, even though it is the summary being displayed in the Reporting Services report at the time of the export. Ideas? Anyone?|||

http://msdn2.microsoft.com/en-us/library/aa178935(SQL.80).aspx

I believe I found the answer to the question of why this report is exporting to the detail. Click on the link above peruse down to this comment, here:

“For matrices, if the matrix is collapsed when viewed in HTML, exporting to Excel expands it. All rows and columns are visible. ”

Part of my confusion comes from being told by the users that this used to work prior to the service pack 2 upgrade. However, I suspect that the summary was never exported to Excel, even prior to the upgrade.

To export with the appropriate summary, I am recommending that the report move from implementing a matrix, to implementing a table for drilldown.

Exports to Excel the details of the report but I need summary

The trouble I am having is that I have a drilldown report that exports the detail to Excel, but I want the summary exported to Excel.

I perform the following steps but get wrong results. Please help me identify the correct steps for the correct results. Thanks you.

1) Select Matrix.

2) Right click, select Properties.

3) Select tab Groups.

4) Select item in Columns list, click Edit.

5) Select tab Visibility.

6) Select Initial visibility: Hidden, and click okay to the Grouping and Sorting dialog box.

Now I can export summary to Excel okay, but now I can not expand the summary in the report itself, so I do the following:

7) Do one through six above (but do not close dialog box), then click visibility can be toggled by another report item.

8) Select the report item in the Report Item drop down list.

Now the report functions normally in the Reporting Services report web page, but when I export on the summary level, again it exports the detail to Excel, but what I want it to export is the summary.

Ideas?

Is this forum active? Only when the drilldown functionality is disabled does the summary export to excel, even though the summary column is calculated from the underlying detail columns. As soon as the drilldown feature is enabled, then the export to excel generates the detail data, even though it is the summary being displayed in the Reporting Services report at the time of the export. Ideas? Anyone?|||

http://msdn2.microsoft.com/en-us/library/aa178935(SQL.80).aspx

I believe I found the answer to the question of why this report is exporting to the detail. Click on the link above peruse down to this comment, here:

“For matrices, if the matrix is collapsed when viewed in HTML, exporting to Excel expands it. All rows and columns are visible. ”

Part of my confusion comes from being told by the users that this used to work prior to the service pack 2 upgrade. However, I suspect that the summary was never exported to Excel, even prior to the upgrade.

To export with the appropriate summary, I am recommending that the report move from implementing a matrix, to implementing a table for drilldown.

Exporting to Excel...problems, problems

I'm exporing a simple matrix report to excel. Once exported I want to sort on
a particular column but it errors out..."This operation requires merged cells
to be identically sized." If I highlight all the cells then go to format ->
cells - > uncheck merge cells it still does not work. The numeric data in the
columns is being treated as text. Can someone please offer some suggestions?
the matrix is quite simple. Person, month columns with the data being the
count per month.
Thanks,Did you try using Data/Text to Columns... on the column of data in question?
"Brian L" wrote:
> I'm exporing a simple matrix report to excel. Once exported I want to sort on
> a particular column but it errors out..."This operation requires merged cells
> to be identically sized." If I highlight all the cells then go to format ->
> cells - > uncheck merge cells it still does not work. The numeric data in the
> columns is being treated as text. Can someone please offer some suggestions?
> the matrix is quite simple. Person, month columns with the data being the
> count per month.
> Thanks,

Exporting to Excel without generating report.

Can a report be exported to an Excel sheet directly without showing it into
my web application?
Thanks a lot! :)Yes, use the URL Access Parameters displayed in the BOL.
&rs:Format=Excel
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Tomas Martinez" <TomasMartinez@.discussions.microsoft.com> schrieb im
Newsbeitrag news:FC958C51-856F-4869-8E95-61C64E61604D@.microsoft.com...
> Can a report be exported to an Excel sheet directly without showing it
> into
> my web application?
> Thanks a lot! :)

Exporting to Excel Tips

Hi !
I am exporting a report to Excel. I have this issue where my labels that
are to the left of my data columns are exported to different rows.
Is there anyone out there can give me some tips or lessons learned when
designing a report that will be exported to Excel?
Thanks,
YI am having a similar problem. I am not using the column headings of the
grid because I need the column headings up in the page header. Instead I
created a row of textboxes that line up with the datagrid up in the header.
It looks great in pdf and html, but as soon as I export to excel some of the
textboxes get pushed down into a lower row. I haven't figured out why yet,
but I think it has something to do with merged cells in excel. If I find
anything I'll post it here.
sebring1130
"Yoshi" wrote:
> Hi !
> I am exporting a report to Excel. I have this issue where my labels that
> are to the left of my data columns are exported to different rows.
> Is there anyone out there can give me some tips or lessons learned when
> designing a report that will be exported to Excel?
> Thanks,
> Y
>
>|||Thanks. I will do the same. Glad to know there are others working on the
same issue.
Take care,
Y
"sebring1130" <sebring1130@.discussions.microsoft.com> wrote in message
news:8F97B4EC-D501-4C9F-B053-D7C867C39332@.microsoft.com...
>I am having a similar problem. I am not using the column headings of the
> grid because I need the column headings up in the page header. Instead I
> created a row of textboxes that line up with the datagrid up in the
> header.
> It looks great in pdf and html, but as soon as I export to excel some of
> the
> textboxes get pushed down into a lower row. I haven't figured out why
> yet,
> but I think it has something to do with merged cells in excel. If I find
> anything I'll post it here.
> sebring1130
>
> "Yoshi" wrote:
>> Hi !
>> I am exporting a report to Excel. I have this issue where my labels that
>> are to the left of my data columns are exported to different rows.
>> Is there anyone out there can give me some tips or lessons learned when
>> designing a report that will be exported to Excel?
>> Thanks,
>> Y
>>

Exporting to excel GridLine,worksheet name,

I am Exporting my report to excel.

1, One thing i want's is to have gridlines available {not by borderstyle } when report is exported to excel.

2,I am inserting page break after a table to put different data on different sheet.How can i name the resultant work sheet {like table1 should be DATA,table2 should be MYSummary}

3,Can I insert page break after any control like simple textbox or it is necessary to put in a table ?

Hello Kamii,

1. I'm not sure if it is possible to turn on the gridlines only when exported since the export is supposed to match the formatting of the report, but someone else might have an idea. Would exporting to CSV work for you?

2. Changing the names of sheets isn't currently supported. Here's a post of the same, with a possible workaround. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=442744&SiteID=1

3. You can't add a page break after a textbox, but you can add one after a Rectangle. So, just create a rectangle, set the 'page break after', then add your textbox inside the rectangle.

Hope this helps.

Jarret

|||

I need these answers too. It would be nice if someone knowledgeable would respond.

Thanks!

Exporting to excel GridLine,worksheet name,

I am Exporting my report to excel.

1, One thing i want's is to have gridlines available {not by borderstyle } when report is exported to excel.

2,I am inserting page break after a table to put different data on different sheet.How can i name the resultant work sheet {like table1 should be DATA,table2 should be MYSummary}

3,Can I insert page break after any control like simple textbox or it is necessary to put in a table ?

Hello Kamii,

1. I'm not sure if it is possible to turn on the gridlines only when exported since the export is supposed to match the formatting of the report, but someone else might have an idea. Would exporting to CSV work for you?

2. Changing the names of sheets isn't currently supported. Here's a post of the same, with a possible workaround. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=442744&SiteID=1

3. You can't add a page break after a textbox, but you can add one after a Rectangle. So, just create a rectangle, set the 'page break after', then add your textbox inside the rectangle.

Hope this helps.

Jarret

|||

I need these answers too. It would be nice if someone knowledgeable would respond.

Thanks!

Exporting to Excel from Preview Tab

I designed a report and from Preview tab, i exported it to Excel format and saved. I sent the Xls file to others, but when they opened it, it is displaying the Metadata info of the file. any idea what is going on?

In my report i have a table, and above it i have a bunch of textboxes which serves as a heading for groups of columns in the table. when i preview it is fine. But Exported to excel, some of these textboxes are wrapping to the next line. any idea what is going on? (I tried aligning all the textboxes)

thanks.

Which version / release of the product are you using? The initial release of RS 2000 did not support older versions of Excel. You can install the second service pack or move to RS 2005.

As for the export, make sure that you are putting the textboxes inside the table header, not as textboxes above the table. This will help you align columns.

Exporting to Excel from Preview Tab

I designed a report and from Preview tab, i exported it to Excel format and
saved. I sent the Xls file to others, but when they opened it, it is
displaying the Metadata info of the file. any idea what is going on?
In my report i have a table, and above it i have a bunch of textboxes which
serves as a heading for groups of columns in the table. when i preview it is
fine. But Exported to excel, some of these textboxes are wrapping to the next
line. any idea what is going on? (I tried aligning all the textboxes)
thanks.Don't know about the second issue but the first issue sounds like you have
not installed either SP1 or SP2. RS initially did not support Excel 2000 or
Excel 97. Starting with SP1 they added support for those version. My guess
is the users you sent the file to are on Excel 2000 or earlier.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Giya" <Giya@.discussions.microsoft.com> wrote in message
news:8B2D6E73-9824-40CC-90DB-5BAEFEFCEA82@.microsoft.com...
>I designed a report and from Preview tab, i exported it to Excel format and
> saved. I sent the Xls file to others, but when they opened it, it is
> displaying the Metadata info of the file. any idea what is going on?
> In my report i have a table, and above it i have a bunch of textboxes
> which
> serves as a heading for groups of columns in the table. when i preview it
> is
> fine. But Exported to excel, some of these textboxes are wrapping to the
> next
> line. any idea what is going on? (I tried aligning all the textboxes)
> thanks.|||thanks.
"Bruce L-C [MVP]" wrote:
> Don't know about the second issue but the first issue sounds like you have
> not installed either SP1 or SP2. RS initially did not support Excel 2000 or
> Excel 97. Starting with SP1 they added support for those version. My guess
> is the users you sent the file to are on Excel 2000 or earlier.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Giya" <Giya@.discussions.microsoft.com> wrote in message
> news:8B2D6E73-9824-40CC-90DB-5BAEFEFCEA82@.microsoft.com...
> >I designed a report and from Preview tab, i exported it to Excel format and
> > saved. I sent the Xls file to others, but when they opened it, it is
> > displaying the Metadata info of the file. any idea what is going on?
> >
> > In my report i have a table, and above it i have a bunch of textboxes
> > which
> > serves as a heading for groups of columns in the table. when i preview it
> > is
> > fine. But Exported to excel, some of these textboxes are wrapping to the
> > next
> > line. any idea what is going on? (I tried aligning all the textboxes)
> >
> > thanks.
>
>

Exporting to Excel 2000

We recently changed over to SQL 2000 RS. Many of our customers are not able
to make sense of a report exported in Office 2000 version of Excel. It is
completely unreadable.
Many are not in the position to be able to Upgrade to Office XP or 2003.
Any ideas on how to help customers with this issue?Make sure you are running SP1 of RS 2000 on the report server and report
designer machines. The Excel rendering extension of SP1 will generate the
Excel output in the BIFF format which is supported by Excel 2000 etc.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"rfoster@.intralearn.com" <rfoster@.intralearn.com@.discussions.microsoft.com>
wrote in message news:F748223F-36E3-4689-A784-6C6445416C2C@.microsoft.com...
> We recently changed over to SQL 2000 RS. Many of our customers are not
> able
> to make sense of a report exported in Office 2000 version of Excel. It is
> completely unreadable.
> Many are not in the position to be able to Upgrade to Office XP or 2003.
> Any ideas on how to help customers with this issue?

Exporting to Excel - OmitFormulas

Hi,
I want to prevent formulas to be exported to Excel. I know it can be done by
Implementing a Rendering Extension for EXCEL but don't know how.
How can it be done for the all reports in the solution?
Thanks.Are you sure that you are exporting the formulas? Because I though I was not
possible to export the formulas. I am typing =sum(Fields!Value.Value) how do
I have to introduce the formula in order to export it?
"dpbobrock" wrote:
> Hi,
> I want to prevent formulas to be exported to Excel. I know it can be done by
> Implementing a Rendering Extension for EXCEL but don't know how.
> How can it be done for the all reports in the solution?
> Thanks.
>

Exporting to Excel

We've noticed that reports exported to excel are much larger than they need to be. Example, report generated and exported (and saved in Excel) shows size of 14,111 KB. However, if same file is saved (using SaveAs in Excel) file is only 4,762KB. Any idea as to why there would be such a size difference? Does RS pass some overhead when exporting to Excel? We are hoping to eliminate any overhead since the time cost during export is rising.

(there are no images being passed, just ~33,000 rows of data)

Thanks.

What method are you using to create the excel files?

|||

We have an ASP front-end that handles some security (report access, restricting what data a user can pass in via parameters) and makes the actual call to the report server for the given report. For most reports, the report parameter is passed to force the report to be exported to Excel (instead of rendering in IE).

So, I run the report, Excel launches and displays the data, and I simply do File/SaveAs... (and rename the file)

Here are some tests I ran against other reports that auto-export to Excel:

ReportA

Test1

Original Spreadsheet: 852k

SaveAs with no changes: 390k

Test2

Original Spreadsheet: 99k

SaveAs with no changes: 52k

Test3

Original Spreadsheet: 365k

SaveAs with no changes: 169k

ReportB

Test1

Original Spreadsheet: 245k

SaveAs with no changes: 104k

Test2

Original Spreadsheet: 365k

SaveAs with no changes: 169k

ReportC

Test1

Original Spreadsheet: 35k

SaveAs with no changes: 34k

Other tests revealed similar results

ReportD

Test1

Original Spreadsheet: 53k

SaveAs with no changes: 49k

Other tests revealed similar results

ReportE

Test1

Original Spreadsheet: 432k

SaveAs with no changes: 293k

Test2

Original Spreadsheet: 14k

SaveAs with no changes: 17k

Test3

Original Spreadsheet: 15k

SaveAs with no changes: 18k

Test4

Original Spreadsheet: 42k

SaveAs with no changes: 38k

Test5

Original Spreadsheet: 51k

SaveAs with no changes: 44k

I find it interesting that the larger the report output size, the greater the difference in sizes when resaved. Also, for very small file sizes, resaved size is actually bigger. Any ideas?

|||

I did some additional research - looks like this is just how Report Server interacts with MS Excel. Report Server cannot take advantage of Excel's file compression process(es) when it exports. Work arounds include exporting first to CSV and then opening the file in Excel OR scheduling the report so that the users don't have to wait. (Another suggestion is to wait for SQL Server 2008 and hope the issue is addressed there.)

I will mark this issue as resolved, but if you have any additional information, please post it here. Thanks.

Exporting the SQL Sever data to ingres

Hi all,

I am having a problem with exporting the data. I have a database in SQL Server which has to be exported in to an ingres database. I was sure that there is no direct option to export the data to ingres, So I tried generating the insert script and cvs files. But the database consists of blobs and images which is not allowing me to create the complete insert script or cvs files.

Does any one know how to resolve this issue?

Thanks in advance,

Vamshi Shekhar CI am moving this to the SQL Server Integration Services forum, which may have some suggestions.

exporting russian and polish text to pdf

Hello,

We have reports in russian and polish which should be exported to pdf, there is no problem when we export them to excell, but when we export them to pdf the fields containing russian and polish caracters are blank.

What can we do to solve this problem?

regards,

bart

try different font