Report Viewer not available in VB Express?

I'm trying to use report viewer controls, but the controls do not appear in the toolbox. The file reportviewer.exe was not in the location specified in the help files, but I have downloaded it, and when I try to add it to the toolbox, I get the message 'ReportViewer.exe' is not a .Net module. Should there be a .dll somewhere? Is it not possible to use this control w/ VB Express / SQLExpress?

ReportViewer.exe contains the dlls for the controls. You need to run it to extract the dlls, and install them in the GAC. See http://msdn2.microsoft.com/en-us/library/ms251723(VS.80).aspx

Report Services Printing from WebBrowser Tool

I have WinForm app that includes a WebBrowser tool from the VisualStudio2005
toolbox. I load a Reporting Services Report into the WinForm's webBrowser
window as follows:
webBrowser1.Navigate(new Uri(reporturl));
This works great, except for when I try to print, I get the following message:
"An error occured trying to get the current window."
Any suggestions for getting a Reporting Service report to print from within
a WinForm's WebBrowser?
Thanks,
--
RandyHello Randy,
If you access the report via the http://, could you print it correctly?
Also, please try to remove the RSClientPrint Class in the IE and check
whether this issue appeared or not.
Remove the RSClientPrint Class from IE:
Tools >> Internet Options >> General Tab >> Settings >> View Objects >>
Right-click
RSClientPrint Class and choose Remove.
If you try to debug the application, what error did you get?
Please let me know the result so that I can provide further assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks for the response.
> If you access the report via the http://, could you print it correctly?
If I access the report using http:// in Internet Explorer, it works
perfectly. If I access the report using http:// in the webBrowser tool in my
WinForm, it gives an error.
> Also, please try to remove the RSClientPrint Class in the IE and check
> whether this issue appeared or not.
I removed the RSClientPrint Class in IE. I get the same results as above.
Printing works in IE, but not in the webBroswer tool in my WinForm.
> If you try to debug the application, what error did you get?
The first error dialog box is as follows:
Print Error:
An error occured trying to get the current window.
<OK>
The second error dialog box:
Error
A Runtime Error has occured.
Do you wish to Debug?
Error: Could not complete the operation due to error 8007f305.
<Yes>
Unable to attach to the crashing process. A debugger is already attached.
<OK>
All thoughts appreicated...
Randy|||Hello Randy,
This is a known issue in the Reporting Services 2005. Please update your
SSRS to SP1 and then have a check.
Thank you!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)