Dropdown width for Multi-select parameters

How can I control the width of the dropdown for multi-select
parameters? It seems to be showing up equal width dropdowns
irrespective of the size of the text. The problem crops up when the
length of the text for any option exceeds the default length, I get an
ugly horizontal scroll bar.
I can have a temporary fix by abbreviating the text content, but that
is not a long-term option.
N.On Feb 20, 1:18 pm, "Nidhee Pathak" <nid...@.gmail.com> wrote:
> How can I control the width of the dropdown for multi-select
> parameters? It seems to be showing up equal width dropdowns
> irrespective of the size of the text. The problem crops up when the
> length of the text for any option exceeds the default length, I get an
> ugly horizontal scroll bar.
> I can have a temporary fix by abbreviating the text content, but that
> is not a long-term option.
> N.
As far as I know, there's not a way to control the width of the drop-
down parameter. That said, it might be possible to modify the
underlying XML in the RDL file in some way that has not been readily
documented.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||What you can do is, you must be using a seperate query for displaying? , so
format / pad with spaces for display field from the sql query, so that the
display field can be in the required size, but the value is same.
Amarnath
"Nidhee Pathak" wrote:
> How can I control the width of the dropdown for multi-select
> parameters? It seems to be showing up equal width dropdowns
> irrespective of the size of the text. The problem crops up when the
> length of the text for any option exceeds the default length, I get an
> ugly horizontal scroll bar.
> I can have a temporary fix by abbreviating the text content, but that
> is not a long-term option.
> N.
>

DROP Temp Table or any scripts

Hi,

What control can I use to put any scripts like that?

ExecuteSQLTask lets me do just sql query.

I need to have something like this.

USE [DB1]

GO

IF EXISTS (SELECT * FROM sys.objects WHERE object_id = OBJECT_ID(N'[dbo].[Lookup]') AND type in (N'U'))

DROP TABLE [dbo].[Lookup]

or Create

CREATE TABLE [Lookup] (
[MD_ID_Old] INTEGER,
[MD_ID_New] uniqueidentifier
)

I need to find the way to use scripts in SSIS.

Thanks.

Have you tried your sql statements in ExecuteSQLTask? This components exists for executing any sql statement. There is a SourceType property that allows you to point to a file [your script] and you can execute the sql statements that way.

Hope this helps...

Senthil

|||Thanks.

Drillthrough Reports not working in Webforms Report Viewer Control

I am using SSRS 2005.
I created a report (Report A) which links to another report (Report B). The
drillthrough works fine both in Visual Studio and via Report Manager.
I have an ASP.NET application which uses the Report Viewer Control to
display Report A. When I click the links in Report A to go to Report B, the
Report Viewer Control/IE shows the hour glass as if something is about to
happen, refreshes the page but still displays Report A.
Obviously the link is set up properly and the reports work since linking
from Report A to Report B works fine from Report Manager.
Are there any known issues with Drillthrough Reports not working in Webforms
Report Viewer Control? Are there any special considerations I should know
about? Any special set up I should be doing?
Any help with this will be greatly appreciated.
--
Chris, SSSIHello Chris,
I have tested on my side that the Drillthrough report works fine on my side.
Here are the steps:
1. Create a new Web Site in the VS 2005.
2. Drag a Report View Control to the Web Page.
3. Click the triangle in the right-up of the Report View Control.
4. Enter the Report Server name and the Report Path of the Drillthough
report.
5. Run the solution and the Drillthough report works fine.
Please try the steps on your side and let me know the result.
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.)|||Wei Lu,
According to your steps I am doing everything correctly, but as I mentioned
in my intial post this is not working.
Can you please answer these questions from my original post:
1) Are there any known issues with Drillthrough Reports not working in
Webforms
Report Viewer Control?
2) Are there any special considerations I should know about?
3) Any special set up I should be doing?
4) What could explain this behavior of the report links not working *ONLY*
in the Report Viewer Control?
Thanks!
-- Chris
Chris, SSSI
"Wei Lu [MSFT]" wrote:
> Hello Chris,
> I have tested on my side that the Drillthrough report works fine on my side.
> Here are the steps:
> 1. Create a new Web Site in the VS 2005.
> 2. Drag a Report View Control to the Web Page.
> 3. Click the triangle in the right-up of the Report View Control.
> 4. Enter the Report Server name and the Report Path of the Drillthough
> report.
> 5. Run the solution and the Drillthough report works fine.
> Please try the steps on your side and let me know the result.
> 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.)
>|||I don't see any attachment. Is it supposed to be attached to your reply?
--
Chris, SSSI
"Wei Lu [MSFT]" wrote:
> Hello Chris,
> So far as I know, there is not any known issue with Drillthrough Reports
> not working in Webforms Report Viewer Control.
> The only thing I do in the VS project is add the ReportViewer control:
> <rsweb:ReportViewer ID="ReportViewer1" runat="server"
> Font-Names="Verdana" Font-Size="8pt"
> Height="400px" ProcessingMode="Remote" Width="692px" >
> <ServerReport ReportPath="/ReportDemo/Drillthrough" />
> </rsweb:ReportViewer>
> The attachement is the sample aspx page.
> Please let me know does this works on your side.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support|||Hello Chris,
OK. I will post the HTML Code of the aspx Page.
============================<%@. Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs"
Inherits="_Default" %>
<%@. Register Assembly="Microsoft.ReportViewer.WebForms, Version=8.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"">http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<rsweb:ReportViewer ID="ReportViewer1" runat="server"
Font-Names="Verdana" Font-Size="8pt"
Height="400px" ProcessingMode="Remote" Width="692px"
DocumentMapCollapsed="True">
<ServerReport ReportPath="/ReportDemo/MultiParameter" />
</rsweb:ReportViewer>
</div>
</form>
</body>
</html>
=============================
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support|||Hi,
It turns out I created my own problem. Chalk it up to lack of experience
with ASP.NET apps. ;-)
The problem was I have code in my code behind page to configure the Report
Viewer control, but I was not checking for a post back condition. When the
user clicks a link to a drill through report a post back is done. As a result
my code behind page was reinitializing the Report Viewer on every user click.
Once I moved that Report Viewer set up code inside a check for "not
postback" everything worked fine.
--
Chris, SSSI
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
>

DrillThrough Report Error: rsInvalidItemPath

RS 2005 rsInvalidItemPath Error.
I am calling a drillthrough report from the ReportViewer control in a
VS 2005 web application. My report structure is as follows:
ParentReport (drillthrough)
ChildReport1(drillthrough)
ChildReport2
I can drill from Parent Report to Child1, but when I drill from Child1
to Child2, I get the following error:
The path of the item "(null)" is not valid. The path must be less than
260 characters long and must start with slash. Other restrictions
apply
Stack-Trace:
Microsoft.Reporting.WebForms.ReportServerException: The path of the
item "(null)" is not valid. The path must be less than 260 characters
long and must start with slash. Other restrictions apply.
(rsInvalidItemPath) at
Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
drillthroughId, String& reportPath) at
Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
drillthroughID) at
Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
actionType, String actionParam, Int32& currentPage, Boolean&
pageSetByEvent, String& navigationID, String& searchText, Int32&
searchStartPage, String& alertMessage, Report& targetReport) at
Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument)
Report Path: /screensave/screensave
Report URL: http://myserver/reportserver
IsDrillThrough: True
I am passing two parameters.
Any recommendations would be much appreciated.
Thanks.On Mar 20, 2:25 pm, "Rob" <rtemp...@.gmail.com> wrote:
> RS 2005 rsInvalidItemPath Error.
> I am calling a drillthrough report from the ReportViewer control in a
> VS 2005 web application. My report structure is as follows:
> ParentReport (drillthrough)
> ChildReport1(drillthrough)
> ChildReport2
> I can drill from Parent Report to Child1, but when I drill from Child1
> to Child2, I get the following error:
> The path of the item "(null)" is not valid. The path must be less than
> 260 characters long and must start with slash. Other restrictions
> apply
> Stack-Trace:
> Microsoft.Reporting.WebForms.ReportServerException: The path of the
> item "(null)" is not valid. The path must be less than 260 characters
> long and must start with slash. Other restrictions apply.
> (rsInvalidItemPath) at
> Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
> drillthroughId, String& reportPath) at
> Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
> drillthroughID) at
> Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
> actionType, String actionParam, Int32& currentPage, Boolean&
> pageSetByEvent, String& navigationID, String& searchText, Int32&
> searchStartPage, String& alertMessage, Report& targetReport) at
> Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHan=dl=ADer.RaisePostBackEvent(String
> eventArgument)
> Report Path: /screensave/screensave
> Report URL:http://myserver/reportserver
> IsDrillThrough: True
> I am passing two parameters.
> Any recommendations would be much appreciated.
> Thanks.
Just to add one more thing, when I run this from Report Manager which
is located on the same machine as the Report Server, I do not get this
error. It must be in the exchange between the reportviewer control on
the web app and the web service on the reportserver. Does anyone know
how this connection takes place in a drill down scenario? I assume
that when the web application (with reportviewer control) makes a call
to the web service, it opens the authenticated connection. Then at
each drill down event, does it make a round trip back to the web app?
It is on the third round trip that I see the error.
Thanks again..|||Hi Rob,
I am getting a similar problem as well. What happens in my case is,
I have a parent report and from it I open the drill down. This works fine as
you pointed out.
I have kept an textbox in the drilled down report which has a hyperlink to
take it back to the parent report. This works fine on the Report server, but
fails on the Web server inside the Report viewer control.
My assumption is that as the viewer opens the page, on subsequent drill
downs, the path keeps on increasing in length and eventually goes above limit.
I will let you know if I find any solution for this. Please keep me posted
as well if you get any solutions yourself.
Harsh
"Rob" wrote:
> On Mar 20, 2:25 pm, "Rob" <rtemp...@.gmail.com> wrote:
> > RS 2005 rsInvalidItemPath Error.
> >
> > I am calling a drillthrough report from the ReportViewer control in a
> > VS 2005 web application. My report structure is as follows:
> >
> > ParentReport (drillthrough)
> > ChildReport1(drillthrough)
> > ChildReport2
> >
> > I can drill from Parent Report to Child1, but when I drill from Child1
> > to Child2, I get the following error:
> >
> > The path of the item "(null)" is not valid. The path must be less than
> > 260 characters long and must start with slash. Other restrictions
> > apply
> >
> > Stack-Trace:
> > Microsoft.Reporting.WebForms.ReportServerException: The path of the
> > item "(null)" is not valid. The path must be less than 260 characters
> > long and must start with slash. Other restrictions apply.
> > (rsInvalidItemPath) at
> > Microsoft.Reporting.WebForms.ServerReport.PerformDrillthrough(String
> > drillthroughId, String& reportPath) at
> > Microsoft.Reporting.WebForms.ReportActionHandler.HandleDrillthrough(String
> > drillthroughID) at
> > Microsoft.Reporting.WebForms.ReportActionHandler.HandleAction(String
> > actionType, String actionParam, Int32& currentPage, Boolean&
> > pageSetByEvent, String& navigationID, String& searchText, Int32&
> > searchStartPage, String& alertMessage, Report& targetReport) at
> > Microsoft.Reporting.WebForms.ReportViewer.System.Web.UI.IPostBackEventHandl­er.RaisePostBackEvent(String
> > eventArgument)
> >
> > Report Path: /screensave/screensave
> > Report URL:http://myserver/reportserver
> > IsDrillThrough: True
> >
> > I am passing two parameters.
> >
> > Any recommendations would be much appreciated.
> >
> > Thanks.
> Just to add one more thing, when I run this from Report Manager which
> is located on the same machine as the Report Server, I do not get this
> error. It must be in the exchange between the reportviewer control on
> the web app and the web service on the reportserver. Does anyone know
> how this connection takes place in a drill down scenario? I assume
> that when the web application (with reportviewer control) makes a call
> to the web service, it opens the authenticated connection. Then at
> each drill down event, does it make a round trip back to the web app?
> It is on the third round trip that I see the error.
> Thanks again..
>

Drill through for visualization control

Is there a way to get the Drill through to work with model viewer controls? Any workaround?

Also, where would I find more complex data mining models for review? SQLServerDataMining site, Microsoft data mining tutorial site, and Data Mining with SQL 2005 book, all checked. Anything else?

-Young K

Do you mean for the redistibutable winform controls or the webform sample controls?

For "more complex models", what kind of models are you looking for?

|||

Support for Drillthrough in the winform viewer controls will be available from Yukon SP2 onwards through a new interface. We'll post a sample on how to use it once SP2 is publicly available.

You can build a complex model using the Movies dataset from sqlserverdatamining.com which has nested tables.

|||

Thanks, Jamie and Shuvro. I'm using winform.

Any idea on when Yukon SP2 is due to be released?

I'm trying to balance the benefit (and complexity) of nested tables vs case table model. You can flatten most scenario into case model for simplicity, but nested model seems to fit better in many cases. Is there accuracy benefit to nested models? What would be rule of the thumb? If you can get away with case table model, stay with case table model?

-Young K

|||

One more thing. What are your thoughts on multi-level nested tables?

-Young K

|||

SP2 will be available the first quarter of 2007. A community technical preview (CTP) build should be available for download within the next few weeks.

Regarding nested tables, I would go with nested tables if your data is in that format. There should be no accuracy difference, there is only a modeling difference. For example, if you have a nested table, an algorithm can "know" that the attributes from the nested table are related to each other. For example I could have "Products Bought in May" and "Products Bought in June".

Additionally I could have multiple columns in my nested table. If I have for example Product Name, Quantity, and Discount, the attributes are already set up that Quantity of Milk is related to Discount of Milk is related to the existence of Milk. The modeling is already done for me.

Another issue is data density. At the case level, the data is "rectangular" - each attribute(column) has the set of values present in the data plus the value "missing". When a NULL value is encountered, the framework sends the "missing" value to the algorithm. (Currently this adds to the total state count whether missing data was encountered or not, which is why it always has a non-zero probability when you look at trees, for example). This means that if there are 100 columns in a case, the frame work will send 100 attributes to the algorithm during training even if most of them are NULL. When you use nested tables, the data is no longer "rectangular" it is "ragged" - e.g. the cases are of variable length. If you have 5 case columns and 95 nested attributes, and a particular case only has 4 attributes in its nested table, the framework will only send 9 attributes to the algorithm. Note that this does add complexity to how the algorithms consume data - i.e. they can't rely on the cases being the same length so the code has to handle many more circumstances, but that's the algorithm developers problem, not the data miners problem.

Finally, nested tables allow you to describe an unlimited number of attributes. Using case columns only, you are essentially limited to the width of your RDBMS - in SQL Server 1024 columns = 1024 attributes. We have test models with 750,000 attributes.

I would use nested tables where natural to do so - it gives you much more flexibility and capability than you may think at first site.

|||

We don't support multi-level nested tables. While way back when we came up with the concept for SQL 2000 data mining we considered it, we discovered that the use cases are too limited and the code would be too complex to make it worthwhile implementing.

The only use case we could think of is examining pages of books that people read. (or objects of a category that are in a particular case) For example I would have a nested table of books and under that I would have a nested table of pages. Each case would only have the pages read by the case level individual.

However, this really posed many questions. Was is that valuable to have the results broken down by book? Your nested table source would look like

CustID BookID Page

You could easily do this without another nested table, unless you wanted to also have information about the page in particular, e.g. reading time, a la

CustID BookID Page ReadingTime

Then you could model the nested -nested table. However, are the complexities added to the language semantics worth this (somewhat limited) use case? Is the workaround of modeling your data such as

CustID (BookID & PageID) ReadingTime

good enough?

In the end we decided that the additional complexities weren't justified at the time. If we get a large enough cohort of customers with production blocking use cases that we just have to have it, then we would definately reconsider. However, considering that the flexibility of nested tables is already leaps and bounds ahead of what is offered elsewhere in the market, I think it would be quite a while before we needed to head down that path.

Thanks

-Jamie

|||

Thank you, Jamie. You are the man.

-Young K.

drill down report with report viewer

Hi
I am using the new report viewer control that comes with Reporting services
2005. However, my reports were created in using Visual Studio 2003 and are
.rdl files. Previously I used jump to url to drill down in a report and
passed the report url along with the report parameters in the query string.
I tried my report using the new report viewer control but when I click on a
drill down link, the report opens in the report viewer but it takes over the
whole IE window. My report viewer is within a page which is within one of
many frames that make up my webb application.
How can I get the drill down to work without losing my other frames?
If this is not possible, what do I need to do to convert my .rdl files to
.rdlc. I understand if I do this that I will need to take the sql query out
of my .rdl report and load up a dataset in code using this query and then
set this as the datasource for the report. Is this correct?
Thanks
Lewis Holmes
eNateHi eNate,
Welcome to use MSDN Managed Newsgroup Support.
From your description, my understanding of this issue is: When you use the
jump to url to view a report in the report viewer control ( SQL Reporting
Services 2005 ), all the frames gones away. If I misundertstood your
concern, please feel free to point it out.
I have tested on my SPS site. But it works fine.
1. I create a Web Page Part, configurate the Report Viewer Control to view
the report. In the report I use jump to url to redirect to another report.
2. I access the Web Page, the report shows fine.
3. I click the link in the report, and it redirected, and the Report Viewer
is fine.
Have you install SPS Service Pack 2? If not , please install and try to
check the issue again.
You can download SP2 from the following site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=171DC9A7-B4BA-4759-
BD64-6B7D851A97EF&displaylang=en
As for the convert from .rdl file to .rdlc file, you may follow this
article:
Converting RDL and RDLC Files
http://msdn2.microsoft.com/en-us/library/ms252109.aspx
Hope this will be helpful
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi
Basically when I click on the link in a report, the report opens in the same
window but the other frames I had are lost.
I have tried using
javascript:void(window.open('reportURLandParameters','_self'));
but this does not work. The closest I have got is to replace '_self' with
the name of the iframe that the report viewer control uses. This works but i
get the report along with the report toolbar are displayed again within the
original report viewer frame. I tried adding &rc:toolbar=false to remove the
toolbar and this works but then the refresh button on the toolbar crashes
with javascript error and print preview thinks the original report page is
still being displayed.
Has anybody got a jump to report URL drill down to open in the report viewer
correctly when using the report viewer within a frame?
I really do not want to have to change the reports at this stage of
development.
I am using .rdl reports and Visual Studio 2005 with ASP.net 2.0.
Thanks
Lewis Holmes
eNate
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:kVKTqgxUGHA.4716@.TK2MSFTNGXA01.phx.gbl...
> Hi eNate,
> Welcome to use MSDN Managed Newsgroup Support.
> From your description, my understanding of this issue is: When you use the
> jump to url to view a report in the report viewer control ( SQL Reporting
> Services 2005 ), all the frames gones away. If I misundertstood your
> concern, please feel free to point it out.
> I have tested on my SPS site. But it works fine.
> 1. I create a Web Page Part, configurate the Report Viewer Control to
> view
> the report. In the report I use jump to url to redirect to another report.
> 2. I access the Web Page, the report shows fine.
> 3. I click the link in the report, and it redirected, and the Report
> Viewer
> is fine.
> Have you install SPS Service Pack 2? If not , please install and try to
> check the issue again.
> You can download SP2 from the following site:
> http://www.microsoft.com/downloads/details.aspx?FamilyId=171DC9A7-B4BA-4759-
> BD64-6B7D851A97EF&displaylang=en
> As for the convert from .rdl file to .rdlc file, you may follow this
> article:
> Converting RDL and RDLC Files
> http://msdn2.microsoft.com/en-us/library/ms252109.aspx
> Hope this will be helpful
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||What happens if you use jump to report instead?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"l.holmes" <enate@.newsgroups.nospam> wrote in message
news:OczKizyUGHA.4976@.TK2MSFTNGP11.phx.gbl...
> Hi
> Basically when I click on the link in a report, the report opens in the
> same window but the other frames I had are lost.
> I have tried using
> javascript:void(window.open('reportURLandParameters','_self'));
> but this does not work. The closest I have got is to replace '_self' with
> the name of the iframe that the report viewer control uses. This works but
> i get the report along with the report toolbar are displayed again within
> the original report viewer frame. I tried adding &rc:toolbar=false to
> remove the toolbar and this works but then the refresh button on the
> toolbar crashes with javascript error and print preview thinks the
> original report page is still being displayed.
> Has anybody got a jump to report URL drill down to open in the report
> viewer correctly when using the report viewer within a frame?
> I really do not want to have to change the reports at this stage of
> development.
> I am using .rdl reports and Visual Studio 2005 with ASP.net 2.0.
> Thanks
> Lewis Holmes
> eNate
>
> "Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
> news:kVKTqgxUGHA.4716@.TK2MSFTNGXA01.phx.gbl...
>> Hi eNate,
>> Welcome to use MSDN Managed Newsgroup Support.
>> From your description, my understanding of this issue is: When you use
>> the
>> jump to url to view a report in the report viewer control ( SQL Reporting
>> Services 2005 ), all the frames gones away. If I misundertstood your
>> concern, please feel free to point it out.
>> I have tested on my SPS site. But it works fine.
>> 1. I create a Web Page Part, configurate the Report Viewer Control to
>> view
>> the report. In the report I use jump to url to redirect to another
>> report.
>> 2. I access the Web Page, the report shows fine.
>> 3. I click the link in the report, and it redirected, and the Report
>> Viewer
>> is fine.
>> Have you install SPS Service Pack 2? If not , please install and try to
>> check the issue again.
>> You can download SP2 from the following site:
>> http://www.microsoft.com/downloads/details.aspx?FamilyId=171DC9A7-B4BA-4759-
>> BD64-6B7D851A97EF&displaylang=en
>> As for the convert from .rdl file to .rdlc file, you may follow this
>> article:
>> Converting RDL and RDLC Files
>> http://msdn2.microsoft.com/en-us/library/ms252109.aspx
>> Hope this will be helpful
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ==================================================>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>