Print Icono

Dear
Why in my reports dont show print icono or print button?
Help me pleaseDid you install Service Pack 2 on your server ?

Print icon not showing up in RS

Has anyone ever seen the print icon not show up in the top toolbar in
Reporting Services? Normally, the print icon shows between the refresh
button and the help button. We saw one instance where the print icon
was not showing: it was just the refresh and help button together. Does
anyone know what could cause this? Is this security related? Thanks.
JustinMy guess is the user of the PC is not in the administrator's group (local
administrators group) and the activeX control is not getting installed.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<jdyer521@.hotmail.com> wrote in message
news:1142869367.565307.13420@.j33g2000cwa.googlegroups.com...
> Has anyone ever seen the print icon not show up in the top toolbar in
> Reporting Services? Normally, the print icon shows between the refresh
> button and the help button. We saw one instance where the print icon
> was not showing: it was just the refresh and help button together. Does
> anyone know what could cause this? Is this security related? Thanks.
> Justin
>

Print data from an ASP.NET ReportViewer that contains multiple pages from FireFox?

Hi,

I have this application in which I am using a number of reports containing one or more pages. When using IE as explorer, the printing button is be?ng displayed properly. When clicking that button, everything works as it should. But when using Firefox as browser, the print button doesn't show up. So I thought about going to the menu of the browser and choose File > Print. The result looks just like a printscreen and when the report contains multiple pages, I am not able to print them in a decent way.

On the internet I read the main reason for this is that Firefox does not work with ActiveX-Objects. In this way it would not be possible to print out the pages!

Can anyone help me out?

Thx a lot!

Recloose!

Anyone?

Print button on toolbar

I have Visual Studio 2005 Standard where I am building a web app. In this
web app I have a Report Viewer and the print button on the toolbar is set to
true, however when I run the app it is not there.
Is this a bug?Not if you are using it in Local Mode. Print is not supported in this mode.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:1855A531-0C20-4625-AE88-9BA151104A03@.microsoft.com...
>I have Visual Studio 2005 Standard where I am building a web app. In this
> web app I have a Report Viewer and the print button on the toolbar is set
> to
> true, however when I run the app it is not there.
> Is this a bug?
>

Print button not showing in Firefox -- ReportViewer control

Hi, I'm having a problem with the ReportViewer control (Reporting Service 2005) in Firefox. Neither the print button nor the Search box are showing up, even when I explicitly set them to be visible. They are showing up fine in IE.

Anyone else had this problem?

When you look at the HTML source, it's clear why it is not showing up. The following code does not even appear in the Firefox version (most important part in bold):

<table cellpadding="0" cellspacing="0" ToolbarSpacer="true" style="display:inline;">
<tr>
<td style="width:20px;"></td>
</tr>
</table>

<div id="RptView_ctl01_ctl07" style="display:inline;font-family:Verdana;font-size:8pt;height:30px;">
<table cellpadding="0" cellspacing="0" style="display:inline;">
<tr>
<td height="28px"><div id="RptView_ctl01_ctl07_ctl00">
<table id="RptView_ctl01_ctl07_ctl00_ctl00" onmouseover="HoverImageRptView_ctl01_ctl07_ctl00_ctl00.OnHover();" onmouseout="HoverImageRptView_ctl01_ctl07_ctl00_ctl00.OnNormal();" title="Print" style="display:none;">
<tr>
<td><input type="image" name="RptView$ctl01$ctl07$ctl00$ctl00$ctl00" src="http://pics.10026.com/?src=/MandateMaker/Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=8.0.50727.42&Name=Icons.Print.gif"onclick="ClientToolbarRptView_ctl01.LoadPrintControl();return false;" style="height:16px;width:16px;border-width:0px;padding:2px;" /></td>
</tr>
</table><script>
HoverImageRptView_ctl01_ctl07_ctl00_ctl00.OnNormal();
</script><table id="RptView_ctl01_ctl07_ctl00_ctl01" onmouseout="HoverImageRptView_ctl01_ctl07_ctl00_ctl01.OnNormal();" title="Print" style="display:inline;">
<tr>
<td><img src="http://pics.10026.com/?src=/MandateMaker/Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=8.0.50727.42&Name=Icons.Print.gif" alt="Print" style="border-width:0px;" /></td>
</tr>
</table><script>
HoverImageRptView_ctl01_ctl07_ctl00_ctl01.OnNormal();
</script>
</div></td>
</tr>
</table>
</div>

<iframe id="PrintFrameRptView_ctl01_ctl07" src="http://pics.10026.com/?src=javascript:''" style="display:none;"></iframe>

Is the "print control" IE-only?

|||I believe that the print controler is an active x controler and that firefox does not suport active x. so yeah the print control would appear to be IE only. however you might be able to find a plugin for firefox that would allow you to run active x|||

Actually, the Microsoft documentation says certain things do not work in non-IE browsers, but the print button is not one of them.

Honest to God, I think Microsoft is just lazy or arrogant sometimes. It's not THAT hard to get printing from a non-IE browser to work. I was able to do it when I had my own custom page to display Reporting Service reports. If I can do it, surely the well-paid gurus at Microsoft can do it!

Grrrrr....I may have to put in code to generate my old custom stuff for non-IE browsers. My custom page does not work as well as the Report Viewer control, so I really would rather not do that.

|||Yeah, it's because they implemented it as an ActiveX control, which is totally the wrong direction to be heading. Microsoft should be moving away from ActiveX since other browsers don't support it (although I think there is a plug-in that allows Firefox to use at least some ActiveX controls). Plus it is a major focal point for security exploits and bugs, it would be better if it was removed from the browser environment entirely.

cs|||

CynthiaD wrote:

Actually, the Microsoft documentation says certain things do not work in non-IE browsers, but the print button is not one of them.

Honest to God, I think Microsoft is just lazy or arrogant sometimes. It's not THAT hard to get printing from a non-IE browser to work. I was able to do it when I had my own custom page to display Reporting Service reports. If I can do it, surely the well-paid gurus at Microsoft can do it!

Grrrrr....I may have to put in code to generate my old custom stuff for non-IE browsers. My custom page does not work as well as the Report Viewer control, so I really would rather not do that.

Hi Cynthia - I know what you are feeling. I moved over most of my clients to LGX Report (www.logixml) because of that issue and similar ones. For most of my clients IE only is not a solution that works. The Logi product is zero footprint and integrates easily with ASP.NET applications. It's also free, but I have one client who needed more features available on their paid version.

Good luck

Steve

|||

Hi,

In my case the print icon is not displayed in the report viewer viewed through the IE.(in the client server)

But able to see the same in our local network

|||Probably security. You are probably allowed to use ActiveX controls in a trusted site (your network), but outside of that the security restrictions prevent using ActiveX controls. If they add your site to the trusted sites in the IE security area, they will likely be able to see the print button. Just my hunch.

cssql

Print button not displayed in report viewer

When i design my report under BIDS(Business Intelligence development studio) i can view the print button of the report

when i use a webapplication i use the reportviewer control installed from C:\\Program files\Microsoft Sql Server\Reporting services...etc.

when i execute the application i dont see the print button displayed

when i checked with the property of reportviewer control the displayprintbutton was set to true but then too the button not present on the form

anything wrong with my installation

plz do help me

thanks

Rama

You are probably printing the report as a LocalReport which does not have a print button the ServerReport does though

|||We had the same issue and installed Reporting services SP2 and it worked.|||

sounded good to me but

I have version 9.00.3054 which I guess is sp2

true I can set the property but I don't get the button

Print button is not visible in rdlc report

I am using client side reports (.rdlc) with ASP.Net 2.0 and SQL Server 2000. Reports are generating fine. But there is no print button on report viewer when i generate report. I use browser's print option to print reports but reports does not get printed properly. Can some one tell me how to enable Print button in client side reports.

Local reports in web apps dont support printing . you should write your own print function for that .

you have to render the report and the print generated emf files .here is a sample code but its in win apps.

you should create your own print function

http://msdn2.microsoft.com/en-us/library/ms252091(VS.80).aspx

Print button generates hugh spooled print files

Hi!
We are currently using a different third party tool to print out pdf-files
generated from SQL Server 2000 Reporting Services. We are a fairly large
international cooperation and have a centralized citrix it environment with
different band width to different places in the world. This makes the print
file size critical.
Because there havenâ't been any really good ways to print out reports before
sp2 we have hoped a lot of the sp2 print functionality. Now itâ's installed in
our test enviromnet and we are pretty disappointed.
It seems like the reports are converted to tiff-format and then printed and
the print file size is huge. We tested to print out a report with six pages
(A4-format) with different techniques and this is the result when it comes to
spooled print file sizes:
1. Using RS print button (14.1 MB)
2. Exporting to TIFF-format from RS and than print (14 MB)
3. Exporting to PDF-format and print with gsprint (ghostscript) using a
windows generic print driver (1.43 MB)
4. Exporting to PDF-format and print with gsprint (ghostscript) using a
print driver specialized for the current printer, hp laserjet (852 KB)
5. Exporting to PDF-format and print with acrobat reader (531 KB)
I have a couple of questions regarding this:
1. Is this right? Is the report converted to TIFF-format when pressing the
print button and is it right that the spooled print file should be this large
and in that case why is it done in this way?
2. Is there any work around for this? Is there any way to get a smaller file?
3. Is this the way it will be implemented in SQL Server 2005 as well?
Regards,
/MattiasHi Mattias,
I also noticed the problem and posted a while back but not got a reply yet
(we too also use Citrix and need to address the bandwidth issue!).
--
Ben
"MattiasT" wrote:
> Hi!
> We are currently using a different third party tool to print out pdf-files
> generated from SQL Server 2000 Reporting Services. We are a fairly large
> international cooperation and have a centralized citrix it environment with
> different band width to different places in the world. This makes the print
> file size critical.
> Because there havenâ't been any really good ways to print out reports before
> sp2 we have hoped a lot of the sp2 print functionality. Now itâ's installed in
> our test enviromnet and we are pretty disappointed.
> It seems like the reports are converted to tiff-format and then printed and
> the print file size is huge. We tested to print out a report with six pages
> (A4-format) with different techniques and this is the result when it comes to
> spooled print file sizes:
> 1. Using RS print button (14.1 MB)
> 2. Exporting to TIFF-format from RS and than print (14 MB)
> 3. Exporting to PDF-format and print with gsprint (ghostscript) using a
> windows generic print driver (1.43 MB)
> 4. Exporting to PDF-format and print with gsprint (ghostscript) using a
> print driver specialized for the current printer, hp laserjet (852 KB)
> 5. Exporting to PDF-format and print with acrobat reader (531 KB)
> I have a couple of questions regarding this:
> 1. Is this right? Is the report converted to TIFF-format when pressing the
> print button and is it right that the spooled print file should be this large
> and in that case why is it done in this way?
> 2. Is there any work around for this? Is there any way to get a smaller file?
> 3. Is this the way it will be implemented in SQL Server 2005 as well?
> Regards,
> /Mattias

Print button generates hugh print files

I have posted this before with no luck so I try again and hope for an answer.
Hi!
We are currently using a different third party tool to print out pdf-files
generated from SQL Server 2000 Reporting Services. We are a fairly large
international cooperation and have a centralized citrix it environment with
different band width to different places in the world. This makes the print
file size critical.
Because there havenâ't been any really good ways to print out reports before
sp2 we have hoped a lot of the sp2 print functionality. Now itâ's installed in
our test enviromnet and we are pretty disappointed.
It seems like the reports are converted to tiff-format and then printed and
the print file size is huge. We tested to print out a report with six pages
(A4-format) with different techniques and this is the result when it comes to
spooled print file sizes:
1. Using RS print button (14.1 MB)
2. Exporting to TIFF-format from RS and than print (14 MB)
3. Exporting to PDF-format and print with gsprint (ghostscript) using a
windows generic print driver (1.43 MB)
4. Exporting to PDF-format and print with gsprint (ghostscript) using a
print driver specialized for the current printer, hp laserjet (852 KB)
5. Exporting to PDF-format and print with acrobat reader (531 KB)
I have a couple of questions regarding this:
1. Is this right? Is the report converted to TIFF-format when pressing the
print button and is it right that the spooled print file should be this large
and in that case why is it done in this way?
2. Is there any work around for this? Is there any way to get a smaller file?
3. Is this the way it will be implemented in SQL Server 2005 as well?
Regards,
/MattiasReports are definitely not output to TIFF format. They are rendered to GDI
(which is a vector format) to send to the printer. I'm not sure what is
behind the size explosion. I will investigate on our side.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"MattiasT" <MattiasT@.discussions.microsoft.com> wrote in message
news:DA2CF65D-D76A-4867-AFED-5A22AB356967@.microsoft.com...
>I have posted this before with no luck so I try again and hope for an
>answer.
> Hi!
> We are currently using a different third party tool to print out pdf-files
> generated from SQL Server 2000 Reporting Services. We are a fairly large
> international cooperation and have a centralized citrix it environment
> with
> different band width to different places in the world. This makes the
> print
> file size critical.
> Because there haven't been any really good ways to print out reports
> before
> sp2 we have hoped a lot of the sp2 print functionality. Now it's installed
> in
> our test enviromnet and we are pretty disappointed.
> It seems like the reports are converted to tiff-format and then printed
> and
> the print file size is huge. We tested to print out a report with six
> pages
> (A4-format) with different techniques and this is the result when it comes
> to
> spooled print file sizes:
> 1. Using RS print button (14.1 MB)
> 2. Exporting to TIFF-format from RS and than print (14 MB)
> 3. Exporting to PDF-format and print with gsprint (ghostscript) using a
> windows generic print driver (1.43 MB)
> 4. Exporting to PDF-format and print with gsprint (ghostscript) using a
> print driver specialized for the current printer, hp laserjet (852 KB)
> 5. Exporting to PDF-format and print with acrobat reader (531 KB)
> I have a couple of questions regarding this:
> 1. Is this right? Is the report converted to TIFF-format when pressing the
> print button and is it right that the spooled print file should be this
> large
> and in that case why is it done in this way?
> 2. Is there any work around for this? Is there any way to get a smaller
> file?
> 3. Is this the way it will be implemented in SQL Server 2005 as well?
> Regards,
> /Mattias
>

print button exists without SP2

In the preeview mode of the report designer the print button and the
print-preeview button are available, activated and can be used.
But this buttons are not displayed if the report is displayed in the IE.
Now I read, that printing will be possible with SP2. Printing is a feature
and not a bug and SPs are supposedly not "Feature Packs".
Printing is a key feature in our project and was suggested. And for the
reason it was to use in the report designer we assumed it works. Now we are
in the testing after a several week development and where is printing?
I realy wish to change my job for a time with the MVPs and MS staff, who are
joking about this subject in this news group. This is nothing to joke about
if you get payed for results and if you are realy responsible for what are
you doing as an self employed developer.
Again I'm realy shoked about the real ripeness of reporting services and the
dimension in which Microsoft is lying by the promotion of there products.Are you asking for help or just being insulting? If you want help I'll try
to help you but instead you just insult MVPs and MS. I have never laughed at
anyone's problem and I help lots of people. And guess what, I don't get paid
to help anyone. I don't see you helping anyone.
That said, I'll help you anyway, although I don't know why I bother. First
off. If you have a print preview button you are using a beta of SP2. That is
fine but a beta means a beta (pre-release) and it sounds to me like you
should not being using a beta product. That said, I can guess what is
happening. SP2 will have two places to install, the development environment
and on the server. It sounds to me like you applied it in the development
environment (hence you see the print button) but did not apply it on the
server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:3CC0DB60-8321-4F86-862D-8E356111EAD0@.microsoft.com...
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we
are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who
are
> joking about this subject in this news group. This is nothing to joke
about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and
the
> dimension in which Microsoft is lying by the promotion of there products.|||Dev Main wrote:
> Again I'm realy shoked about the real ripeness of reporting services
> and the dimension in which Microsoft is lying by the promotion of
> there products.
Devmaaan,
i waste my time with reading you confuse posts.
Please!...let it be and develop your reports with an other software.
Did you pay for reporting services? I assume that you dont licensed a
sql-server-license only for reporting...hmm?
regards
frank|||Is this really the place to whine about Microsoft putting features into
Service Packs? I thought this was a place for answers not a place to
discuss your plight as a self employed developer. I have only witnessed
helpfulness from the Microsoft guys. We not me personally as I try to
help answer questions rather than ask them. I try to contribute not
just tear down and whine about what is in or not in Reporting Services.
I have 2 things to point out. 1) Reporting Services is basically
free...although there are some qualifications to that statement. 2)
Reporting Services is in version 1 still.
You aren't much of a developer if you don't have a little bit of
respect for a version 1 product. Maybe DevMain, you need to be less
critical and more helpful. We all have our issues...but we are working
together to resolve them. That is what this group is for...not for your
destructive criticism of people who are just trying to help.
And just as I though (as I look at your other postings) you are the
same guy that is "Shoked" about something else. Dude...buy
Crystal...see if they care...and let the Reporting Services bus roll
on without you. You get too "shoked" all of the time...and by the
way...I believe it's Shocked...not shoked...I have no idea what shoked
is.
And last...incase you are wondering...I am not employed by Microsoft. I
am just a guy trying to get answers to a product that I really like.|||SP2 is coming out shortly and the long awaited client side printing
functionality will be there.
You should really familiarize yourself with the features list of a release
before architecting and developing a solution. It'll help you avoid
surprises.
Also, you may not want to lash out at the very people who can probably
answers your technical questions.
--
Adrian M.
MCP
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:3CC0DB60-8321-4F86-862D-8E356111EAD0@.microsoft.com...
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we
> are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who
> are
> joking about this subject in this news group. This is nothing to joke
> about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and
> the
> dimension in which Microsoft is lying by the promotion of there products.|||It is not true that I don't help others! There are articles I wrote answeres.
But I like to become a bit more expert in the subject before teaching others
how to do something.
"You love the product and I have no respect for a version 1.0".
I'm responsible in real live projects for predictable results in a
predictable time. And from the facts I will describe belowe Reporting
Services is a promissing beta version with potential for a great product.
Promise: Reports can be exported to excel and the data can be processed there.
Reality: With "can grow" option on fields the layout in excel is unusable.
Sort function doesn't work on export to excel (not to csv). (Excel XP!). On
CSV Export the fields become seperated with a "," what is not supported by
Excel and not supported by Access and is stupid too, becouse whats about ","
in the field values?
Promise: Group report data like in MS Access
Reality: With the list control ("the one for Access users"). Nested list
controls makes the report frequently corrupt. If the fields are located
without distance between it, the fields displayed somewhere in the page. If I
place them with a distance between them the formating in excel is unusefull.
Promise: Reporting Services provides Parameters
Realitiy:
- The parameter captions can not be localizesed.
- The dropdown lists can not be localizesed.
- With cascading parameters the dropdownlists are requeried, even if thy are
not depend on a selected field.
- The dropdownlist are requeried when the report get rendered.
- If several parameters depend all on the same other parameter each
selection in one of the drop down list couse all drop downlists beeing
requeried. With 6 parameters I've got the drop down lists 26 times requeried,
but only 5 times are necessary.
- Multiple selection are relized by enter the values manualy by the user
(Tip from MVPs)
Promise: Localization
Reality: Localization is not possible! What ever you say it is not in real
live projects. You can't localize report names and descriptions in the report
manager. You can't localize Parameter captions or drop down lists. You can't
implement a language selection for the user. And much more. The solution is
to build your own report manager in a asp application and provide for the
parameter input separat forms.
Promise: Printing reports. From the promotion everybody I'm talking about
expected to print out a report. I think I read this feature, but in this
moment I don't find it again. Two members of our project team said they read
it too.
Promisse: Custom assembly
Realitity: I replaced it with a update, but reporting services still used
the previous version. How comes this, if I replaced physicaly the file? Ahhh
there is a copy of the file somewhere in "...\.net Framework\...\temp"
directory. "Oh chef, I don't achived the result I promised! But I found
something out tonight what makes me love the Microsoft product much more then
my family. Could I get a salary increase?"
I could enumerate much more issues.
That the product is for free is no argument. In our case we purchased a SQL
Server license only to use reporting services. The data are hosted in a
oracle database. And independend from if it costs something or not, it is not
my fault that it is for free and if it would be not for free we have
purchased it.
About the printing function I found in the middle of my dispair a post from
a MVP posted in October where he wrote that the user should pray to good and
this brings the service pack 2 possibly to chrismas.
Reality:
"Dev Main" wrote:
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who are
> joking about this subject in this news group. This is nothing to joke about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and the
> dimension in which Microsoft is lying by the promotion of there products.|||Send a description of the problems/issues you have noticed to:
mswish@.microsoft.com
http://www.microsoft.com/mswish
Adrian M.
MCP
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:DAE6F1C5-7614-46AB-97F5-B9287B8D192B@.microsoft.com...
> It is not true that I don't help others! There are articles I wrote
> answeres.
> But I like to become a bit more expert in the subject before teaching
> others
> how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great product.
> Promise: Reports can be exported to excel and the data can be processed
> there.
> Reality: With "can grow" option on fields the layout in excel is unusable.
> Sort function doesn't work on export to excel (not to csv). (Excel XP!).
> On
> CSV Export the fields become seperated with a "," what is not supported by
> Excel and not supported by Access and is stupid too, becouse whats about
> ","
> in the field values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested list
> controls makes the report frequently corrupt. If the fields are located
> without distance between it, the fields displayed somewhere in the page.
> If I
> place them with a distance between them the formating in excel is
> unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if thy
> are
> not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists beeing
> requeried. With 6 parameters I've got the drop down lists 26 times
> requeried,
> but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the user
> (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in real
> live projects. You can't localize report names and descriptions in the
> report
> manager. You can't localize Parameter captions or drop down lists. You
> can't
> implement a language selection for the user. And much more. The solution
> is
> to build your own report manager in a asp application and provide for the
> parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking about
> expected to print out a report. I think I read this feature, but in this
> moment I don't find it again. Two members of our project team said they
> read
> it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still used
> the previous version. How comes this, if I replaced physicaly the file?
> Ahhh
> there is a copy of the file somewhere in "...\.net Framework\...\temp"
> directory. "Oh chef, I don't achived the result I promised! But I found
> something out tonight what makes me love the Microsoft product much more
> then
> my family. Could I get a salary increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased a
> SQL
> Server license only to use reporting services. The data are hosted in a
> oracle database. And independend from if it costs something or not, it is
> not
> my fault that it is for free and if it would be not for free we have
> purchased it.
> About the printing function I found in the middle of my dispair a post
> from
> a MVP posted in October where he wrote that the user should pray to good
> and
> this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
>> In the preeview mode of the report designer the print button and the
>> print-preeview button are available, activated and can be used.
>> But this buttons are not displayed if the report is displayed in the IE.
>> Now I read, that printing will be possible with SP2. Printing is a
>> feature
>> and not a bug and SPs are supposedly not "Feature Packs".
>> Printing is a key feature in our project and was suggested. And for the
>> reason it was to use in the report designer we assumed it works. Now we
>> are
>> in the testing after a several week development and where is printing?
>> I realy wish to change my job for a time with the MVPs and MS staff, who
>> are
>> joking about this subject in this news group. This is nothing to joke
>> about
>> if you get payed for results and if you are realy responsible for what
>> are
>> you doing as an self employed developer.
>> Again I'm realy shoked about the real ripeness of reporting services and
>> the
>> dimension in which Microsoft is lying by the promotion of there products.|||If you have a question, next time post the question and people will try to
help. You were very insulting last time.
Let me be very very clear here because you missed the point again. Printing
from the client will be released with SP2 (Service Pack 2). This will be
released this month.
Point number 2. It is a release 1 product. Certain things are hard to do (I
am currently working around an Excel issue) so yes, there are issues. So far
I have seen that most issues have a work around (most but not all).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:DAE6F1C5-7614-46AB-97F5-B9287B8D192B@.microsoft.com...
> It is not true that I don't help others! There are articles I wrote
answeres.
> But I like to become a bit more expert in the subject before teaching
others
> how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great product.
> Promise: Reports can be exported to excel and the data can be processed
there.
> Reality: With "can grow" option on fields the layout in excel is unusable.
> Sort function doesn't work on export to excel (not to csv). (Excel XP!).
On
> CSV Export the fields become seperated with a "," what is not supported by
> Excel and not supported by Access and is stupid too, becouse whats about
","
> in the field values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested list
> controls makes the report frequently corrupt. If the fields are located
> without distance between it, the fields displayed somewhere in the page.
If I
> place them with a distance between them the formating in excel is
unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if thy
are
> not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists beeing
> requeried. With 6 parameters I've got the drop down lists 26 times
requeried,
> but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the user
> (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in real
> live projects. You can't localize report names and descriptions in the
report
> manager. You can't localize Parameter captions or drop down lists. You
can't
> implement a language selection for the user. And much more. The solution
is
> to build your own report manager in a asp application and provide for the
> parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking about
> expected to print out a report. I think I read this feature, but in this
> moment I don't find it again. Two members of our project team said they
read
> it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still used
> the previous version. How comes this, if I replaced physicaly the file?
Ahhh
> there is a copy of the file somewhere in "...\.net Framework\...\temp"
> directory. "Oh chef, I don't achived the result I promised! But I found
> something out tonight what makes me love the Microsoft product much more
then
> my family. Could I get a salary increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased a
SQL
> Server license only to use reporting services. The data are hosted in a
> oracle database. And independend from if it costs something or not, it is
not
> my fault that it is for free and if it would be not for free we have
> purchased it.
> About the printing function I found in the middle of my dispair a post
from
> a MVP posted in October where he wrote that the user should pray to good
and
> this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
> > In the preeview mode of the report designer the print button and the
> > print-preeview button are available, activated and can be used.
> >
> > But this buttons are not displayed if the report is displayed in the IE.
> >
> > Now I read, that printing will be possible with SP2. Printing is a
feature
> > and not a bug and SPs are supposedly not "Feature Packs".
> >
> > Printing is a key feature in our project and was suggested. And for the
> > reason it was to use in the report designer we assumed it works. Now we
are
> > in the testing after a several week development and where is printing?
> >
> > I realy wish to change my job for a time with the MVPs and MS staff, who
are
> > joking about this subject in this news group. This is nothing to joke
about
> > if you get payed for results and if you are realy responsible for what
are
> > you doing as an self employed developer.
> >
> > Again I'm realy shoked about the real ripeness of reporting services and
the
> > dimension in which Microsoft is lying by the promotion of there
products.|||Dev Main, you need to chill out man.
RS was released early because of user pressure. MS weren't planning to
release it until SQL2005. Considering that, it's a suprisingly good
release.
Yes it is limited in some areas, like printing, but exporting to PDF is
a satisfactory compromise for most.
RS is designed as a web based tool so printing is not it's main reason
for existence.
If you want to control reporting centrally and deploy to intranet, it's
the best tool for the job. It does require database knowledge and VB
knowledge helps too. MS make no secret of that.
You CAN localise, it might require some effort but it can be done.
As for Access Reporting, you just can't compare RS with Access
reporting, they are aimed at completely different audiences.
Excel export works OK for most cases, but there are issues.
The comma in a field issue with CSV is a perrenial CSV problem, but
surround text with delimiters, e.g. Quotes " and it's OK. This isn't an
RS issue.
I have my suspicions that as an Oracle devotee you are fairly anti-MS.
I don't have a problem with that, but I do feel you're being a little
unfair to the RS team with your rant. For once, Microsofts claim to be
'innovative' is bourne out by this product, give them a break.
Like any application, you need to evaluate it. It's not suitable for
all situations or organisations but don't have a go at them if that's
the case, work with them, they will help.
FYI: The print feature is coming imminently with SP2.
Regards
Chris
Dev Main wrote:
> It is not true that I don't help others! There are articles I wrote
> answeres. But I like to become a bit more expert in the subject
> before teaching others how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great
> product.
> Promise: Reports can be exported to excel and the data can be
> processed there. Reality: With "can grow" option on fields the
> layout in excel is unusable. Sort function doesn't work on export to
> excel (not to csv). (Excel XP!). On CSV Export the fields become
> seperated with a "," what is not supported by Excel and not supported
> by Access and is stupid too, becouse whats about "," in the field
> values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested
> list controls makes the report frequently corrupt. If the fields are
> located without distance between it, the fields displayed somewhere
> in the page. If I place them with a distance between them the
> formating in excel is unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if
> thy are not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists
> beeing requeried. With 6 parameters I've got the drop down lists 26
> times requeried, but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the
> user (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in
> real live projects. You can't localize report names and descriptions
> in the report manager. You can't localize Parameter captions or drop
> down lists. You can't implement a language selection for the user.
> And much more. The solution is to build your own report manager in a
> asp application and provide for the parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking
> about expected to print out a report. I think I read this feature,
> but in this moment I don't find it again. Two members of our project
> team said they read it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still
> used the previous version. How comes this, if I replaced physicaly
> the file? Ahhh there is a copy of the file somewhere in "...\.net
> Framework\...\temp" directory. "Oh chef, I don't achived the result I
> promised! But I found something out tonight what makes me love the
> Microsoft product much more then my family. Could I get a salary
> increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased
> a SQL Server license only to use reporting services. The data are
> hosted in a oracle database. And independend from if it costs
> something or not, it is not my fault that it is for free and if it
> would be not for free we have purchased it.
> About the printing function I found in the middle of my dispair a
> post from a MVP posted in October where he wrote that the user should
> pray to good and this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
> > In the preeview mode of the report designer the print button and
> > the print-preeview button are available, activated and can be used.
> >
> > But this buttons are not displayed if the report is displayed in
> > the IE.
> >
> > Now I read, that printing will be possible with SP2. Printing is a
> > feature and not a bug and SPs are supposedly not "Feature Packs".
> >
> > Printing is a key feature in our project and was suggested. And for
> > the reason it was to use in the report designer we assumed it
> > works. Now we are in the testing after a several week development
> > and where is printing?
> >
> > I realy wish to change my job for a time with the MVPs and MS
> > staff, who are joking about this subject in this news group. This
> > is nothing to joke about if you get payed for results and if you
> > are realy responsible for what are you doing as an self employed
> > developer.
> >
> > Again I'm realy shoked about the real ripeness of reporting
> > services and the dimension in which Microsoft is lying by the
> > promotion of there products.|||I would gather by the difficulty that I have reading your posts that
the issues you are having with your reports are users/developer
issues...not so much the product.
I would fire whoever it was in your organization that evaluated SRS and
had you guys buy SQL just for reporting services...as it doesn't sound
like the product fulfills your needs.
I would not however, complain because the product doesn't fit my needs.
I would find a better product or be patient like the rest of us until
the next release which shall provide more functionality.
You make a lot of criticisms...most of which I have to read 3 times to
understand...and some of which are unfounded. Like ANY product, you are
going to have to find work arounds...as a developer you should know
this.
I have known many a bad developer...in a lot of circles I am problem
one of them...and they all blame their incompetence on the product.
One day there shall be a product that fulfills every need...and bad
developers won't have anything to complain about.
I can't wait for your next installment...as I am just about done with
my decoder.
Lukesql

Print button doesn't work in ReportServer 2005

I can preview reports on the server fine. The first time I clicked the
print button, I got a message asking me to install SQL Server? I said
yes, then after a few minutes I got a print error.
Now, every time I click the print button on the RS toolbar, I get this
message:
Print Error
An error occured trying to get the current window.
Besides the fact that occurred is spelled wrong, why is this error
happening? I tried deleting all RSClient* files from \Windows\Downloaded
Program Files, but that doesn't help.
How do I fix this?
TIA,
Mike RodriguezCan you try deleting the ActiveX control via IE.
Go to Tools->Internet Options
Click the Settings button
Click the View Objects button.
Delete the RSClientPrint control
I would also clear out my internet cache to make sure you are getting the
latest cab file.
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>I can preview reports on the server fine. The first time I clicked the
>print button, I got a message asking me to install SQL Server? I said
>yes, then after a few minutes I got a print error.
> Now, every time I click the print button on the RS toolbar, I get this
> message:
> Print Error
> An error occured trying to get the current window.
> Besides the fact that occurred is spelled wrong, why is this error
> happening? I tried deleting all RSClient* files from \Windows\Downloaded
> Program Files, but that doesn't help.
> How do I fix this?
> TIA,
> Mike Rodriguez
>|||Hi Daniel,
Ok, I did that. Unfortunately, I still get the same error.
Any other ideas?
Mike
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
> Can you try deleting the ActiveX control via IE.
> Go to Tools->Internet Options
> Click the Settings button
> Click the View Objects button.
> Delete the RSClientPrint control
> I would also clear out my internet cache to make sure you are getting the
> latest cab file.
>
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from \Windows\Downloaded
>> Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>|||Are you viewing reports through a hosted IE control? That is is this a
winforms app or are your going to the ReportServer through IE?
If it is in a hosted win forms then this is expected and the print
functionality is not supported there.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Rodriguez" <mike@.nospam.com> wrote in message
news:etvrvsC$FHA.2036@.TK2MSFTNGP14.phx.gbl...
> Hi Daniel,
> Ok, I did that. Unfortunately, I still get the same error.
> Any other ideas?
> Mike
>
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
>> Can you try deleting the ActiveX control via IE.
>> Go to Tools->Internet Options
>> Click the Settings button
>> Click the View Objects button.
>> Delete the RSClientPrint control
>> I would also clear out my internet cache to make sure you are getting the
>> latest cab file.
>>
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from
>> \Windows\Downloaded Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>>
>|||Hi Daniel,
Actually, the print button works in my winforms app. It doesn't work in the
IE web application that ReportServer created for me.
What can I do?
Mike
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:OwcNYeE$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Are you viewing reports through a hosted IE control? That is is this a
> winforms app or are your going to the ReportServer through IE?
> If it is in a hosted win forms then this is expected and the print
> functionality is not supported there.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Michael Rodriguez" <mike@.nospam.com> wrote in message
> news:etvrvsC$FHA.2036@.TK2MSFTNGP14.phx.gbl...
>> Hi Daniel,
>> Ok, I did that. Unfortunately, I still get the same error.
>> Any other ideas?
>> Mike
>>
>> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
>> news:eO9RFNC$FHA.216@.TK2MSFTNGP15.phx.gbl...
>> Can you try deleting the ActiveX control via IE.
>> Go to Tools->Internet Options
>> Click the Settings button
>> Click the View Objects button.
>> Delete the RSClientPrint control
>> I would also clear out my internet cache to make sure you are getting
>> the latest cab file.
>>
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Michael Rodriguez" <mike@.nospam.com> wrote in message
>> news:eb%23LX2B$FHA.3636@.TK2MSFTNGP10.phx.gbl...
>>I can preview reports on the server fine. The first time I clicked the
>>print button, I got a message asking me to install SQL Server? I said
>>yes, then after a few minutes I got a print error.
>> Now, every time I click the print button on the RS toolbar, I get this
>> message:
>> Print Error
>> An error occured trying to get the current window.
>> Besides the fact that occurred is spelled wrong, why is this error
>> happening? I tried deleting all RSClient* files from
>> \Windows\Downloaded Program Files, but that doesn't help.
>> How do I fix this?
>> TIA,
>> Mike Rodriguez
>>
>>
>>
>

Print Button - ActiveX Installation

Hello,
How can I deploy the ActiveX to the workstations?
The users don't have administrative privileges, I want to install the active
X control before they click the print button.
Is there a way to download the files of instalation and run some setup?
ThanksRS doesn't supply any mechanism for doing this. What you could do is look
for the rsclientprint.cab file and extract its information. Then copy it to
the users "WINDOWS\Downloaded Program Files" folder. This should allow the
users the ability to use the control without downloading it. Of course you
would need to do all the maintenance for updating the control if it every
changes.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Armand Charles" <armand.charles@.tty.com.br> wrote in message
news:eCG$imXAGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hello,
> How can I deploy the ActiveX to the workstations?
> The users don't have administrative privileges, I want to install the
> active X control before they click the print button.
> Is there a way to download the files of instalation and run some setup?
> Thanks
>|||Hi Daniel
I can't copy the extract files of rsclientprint.cab to "WINDOWS\Downloaded
Program Files", it doesn't work. This folder looks as read only.
Thank you for your response,
Armand
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> escreveu na mensagem
news:uGHFVdaAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> RS doesn't supply any mechanism for doing this. What you could do is look
> for the rsclientprint.cab file and extract its information. Then copy it
> to the users "WINDOWS\Downloaded Program Files" folder. This should allow
> the users the ability to use the control without downloading it. Of
> course you would need to do all the maintenance for updating the control
> if it every changes.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Armand Charles" <armand.charles@.tty.com.br> wrote in message
> news:eCG$imXAGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hello,
>> How can I deploy the ActiveX to the workstations?
>> The users don't have administrative privileges, I want to install the
>> active X control before they click the print button.
>> Is there a way to download the files of instalation and run some setup?
>> Thanks
>|||You can do it, you just need to do it via the command line.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Armand Charles" <armand.charles@.tty.com.br> wrote in message
news:%23RDSW1MBGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi Daniel
> I can't copy the extract files of rsclientprint.cab to "WINDOWS\Downloaded
> Program Files", it doesn't work. This folder looks as read only.
> Thank you for your response,
> Armand
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> escreveu na mensagem
> news:uGHFVdaAGHA.1312@.TK2MSFTNGP09.phx.gbl...
>> RS doesn't supply any mechanism for doing this. What you could do is
>> look for the rsclientprint.cab file and extract its information. Then
>> copy it to the users "WINDOWS\Downloaded Program Files" folder. This
>> should allow the users the ability to use the control without downloading
>> it. Of course you would need to do all the maintenance for updating the
>> control if it every changes.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Armand Charles" <armand.charles@.tty.com.br> wrote in message
>> news:eCG$imXAGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hello,
>> How can I deploy the ActiveX to the workstations?
>> The users don't have administrative privileges, I want to install the
>> active X control before they click the print button.
>> Is there a way to download the files of instalation and run some setup?
>> Thanks
>>
>|||Would you please tell me what have I missed? I already copied the files to
"WINDOWS\Downloaded Program Files" folder. It still asks me to intall
Reporting Services when I click the PRINT button.
Thanks,
Anna
"Daniel Reib [MSFT]" wrote:
> You can do it, you just need to do it via the command line.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Armand Charles" <armand.charles@.tty.com.br> wrote in message
> news:%23RDSW1MBGHA.2320@.TK2MSFTNGP11.phx.gbl...
> > Hi Daniel
> >
> > I can't copy the extract files of rsclientprint.cab to "WINDOWS\Downloaded
> > Program Files", it doesn't work. This folder looks as read only.
> >
> > Thank you for your response,
> >
> > Armand
> >
> > "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> escreveu na mensagem
> > news:uGHFVdaAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> >> RS doesn't supply any mechanism for doing this. What you could do is
> >> look for the rsclientprint.cab file and extract its information. Then
> >> copy it to the users "WINDOWS\Downloaded Program Files" folder. This
> >> should allow the users the ability to use the control without downloading
> >> it. Of course you would need to do all the maintenance for updating the
> >> control if it every changes.
> >>
> >> --
> >> -Daniel
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Armand Charles" <armand.charles@.tty.com.br> wrote in message
> >> news:eCG$imXAGHA.2320@.TK2MSFTNGP11.phx.gbl...
> >> Hello,
> >>
> >> How can I deploy the ActiveX to the workstations?
> >> The users don't have administrative privileges, I want to install the
> >> active X control before they click the print button.
> >> Is there a way to download the files of instalation and run some setup?
> >>
> >> Thanks
> >>
> >>
> >>
> >
> >
>
>|||I got the same problem too. I was using WinInstall and found that it got lots of registry entries. Do anyone know how to deploy it.
From http://www.developmentnow.com/g/115_2005_12_0_0_679249/Print-Button--ActiveX-Installation.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Print Button

Print button is disabled for some users. Don't know why it is doing so? Works fine for most of the users in the same group.

Any help is much appreciated.

SQL SERVER Reporting Services 2000

Win XP

check whether any printer drivers are installed in the machine.

if no printers are installed, then print button gets disabled

suresh babu k

|||

Thank you much! I will check that.

|||Actually printer is installed. But still print button is greyed out.|||

Also check the RSPRINTCLIENT control in the C:\WINDOWS\Downloaded Program Files folder. I they ran on the beta then this dll could be very old. It doesn't seem to get updated when the server does. You can remove it and RS will download a new one.

Although I don't think this will cause the print button to be dimmed out. But if you have a printer installed and its a valid driver, you should get the button at least.

|||R U using rdl or rdlc files..... ?|||

We are using rdl files.

Thanks

|||

The print button is disabled if the users in question cannot download and install the RS Printing ActiveX control.

We have several users who run as non-admin accounts. You have to log onto their machines as an admin and then print the report once. After that the ActiveX control is installed and it works for them.

|||Is there anyway of removing the Print functionality of Report Manager i.e. disabling printing directly from Report Manager?
This in RS 2005
|||

The solution is documented here:

http://msdn2.microsoft.com/en-us/library/ms155874.aspx

-Lukasz

Print Button

I have a web application with a stand alone report. When I put the ReportViewer in the webform I can see every reports in the project. The problem is that I can't see the print report button...

If I indicate that the report is a "Server Report" instead a local report the Print Report appear, but a need a "Local Report" not a "Server Report" How can i solve that.

Thank you.The ASP.NET version of the ReportViewer control does not support client print (which is accomplished with an ActiveX control) in local mode. We are considering adding this in a future release.

Print Button

Print button is disabled for some users. Don't know why it is doing so? Works fine for most of the users in the same group.

Any help is much appreciated.

SQL SERVER Reporting Services 2000

Win XP

check whether any printer drivers are installed in the machine.

if no printers are installed, then print button gets disabled

suresh babu k

|||

Thank you much! I will check that.

|||Actually printer is installed. But still print button is greyed out.|||

Also check the RSPRINTCLIENT control in the C:\WINDOWS\Downloaded Program Files folder. I they ran on the beta then this dll could be very old. It doesn't seem to get updated when the server does. You can remove it and RS will download a new one.

Although I don't think this will cause the print button to be dimmed out. But if you have a printer installed and its a valid driver, you should get the button at least.

|||R U using rdl or rdlc files..... ?|||

We are using rdl files.

Thanks

|||

The print button is disabled if the users in question cannot download and install the RS Printing ActiveX control.

We have several users who run as non-admin accounts. You have to log onto their machines as an admin and then print the report once. After that the ActiveX control is installed and it works for them.

|||Is there anyway of removing the Print functionality of Report Manager i.e. disabling printing directly from Report Manager?
This in RS 2005
|||

The solution is documented here:

http://msdn2.microsoft.com/en-us/library/ms155874.aspx

-Lukasz

sql