Monday, March 12, 2012
Is there other control like ReportViewer control to avoid security problems
i am using ReportViewer Control to view the SQL REPORT in the aspx page
its working fine and i am able to view the reports..
Now The problem is that
ReportViewer needs direct access to the Database Server
(i mean to say, we need to give the serverURL(database) to the
reportviewer )
but at my client place the web application is installed on one
server(which is configured to public IP) and the database is on other
server(which is not publicIP)
So when i try to view the report from my web application i am getting
error "page not Found"
can any one please tell me the way to view the reports in my web page
with other than reportviewer.. which gives the same functionality and
which can overcome these sort of security issues
thanx
anil...Not sure if it's a bad practice but before I knew about the ReportViewer I
used an <iframe> and displayed it in that...
It worked fine and should help you with your problem.
Regards
--
http://dotnet.org.za/stanley
"anil" wrote:
> Hello Friends
> i am using ReportViewer Control to view the SQL REPORT in the aspx page
> its working fine and i am able to view the reports..
> Now The problem is that
> ReportViewer needs direct access to the Database Server
> (i mean to say, we need to give the serverURL(database) to the
> reportviewer )
> but at my client place the web application is installed on one
> server(which is configured to public IP) and the database is on other
> server(which is not publicIP)
> So when i try to view the report from my web application i am getting
> error "page not Found"
> can any one please tell me the way to view the reports in my web page
> with other than reportviewer.. which gives the same functionality and
> which can overcome these sort of security issues
> thanx
> anil...
>|||Hello Stan, thanx for the info
i would like to know some more info reg.
by using <iframe> how can i redirect the request to the database
server...
do u have any idea.. or examples pls let me know ..
thanx & regards
Stan wrote:
> Not sure if it's a bad practice but before I knew about the ReportViewer I
> used an <iframe> and displayed it in that...
> It worked fine and should help you with your problem.
> Regards
> --
> http://dotnet.org.za/stanley
>
> "anil" wrote:
> > Hello Friends
> >
> > i am using ReportViewer Control to view the SQL REPORT in the aspx page
> > its working fine and i am able to view the reports..
> >
> > Now The problem is that
> >
> > ReportViewer needs direct access to the Database Server
> > (i mean to say, we need to give the serverURL(database) to the
> > reportviewer )
> > but at my client place the web application is installed on one
> > server(which is configured to public IP) and the database is on other
> > server(which is not publicIP)
> > So when i try to view the report from my web application i am getting
> > error "page not Found"
> >
> > can any one please tell me the way to view the reports in my web page
> > with other than reportviewer.. which gives the same functionality and
> > which can overcome these sort of security issues
> >
> > thanx
> > anil...
> >
> >|||IFrame will have the same problem. You need to use webservices in your web
app. Or, using VS 2005 web control (which itself uses web services) supports
this configuration.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"anil" <kumar.vanaparthy@.gmail.com> wrote in message
news:1130364685.976063.324410@.g43g2000cwa.googlegroups.com...
> Hello Stan, thanx for the info
> i would like to know some more info reg.
> by using <iframe> how can i redirect the request to the database
> server...
> do u have any idea.. or examples pls let me know ..
> thanx & regards
>
> Stan wrote:
>> Not sure if it's a bad practice but before I knew about the ReportViewer
>> I
>> used an <iframe> and displayed it in that...
>> It worked fine and should help you with your problem.
>> Regards
>> --
>> http://dotnet.org.za/stanley
>>
>> "anil" wrote:
>> > Hello Friends
>> >
>> > i am using ReportViewer Control to view the SQL REPORT in the aspx page
>> > its working fine and i am able to view the reports..
>> >
>> > Now The problem is that
>> >
>> > ReportViewer needs direct access to the Database Server
>> > (i mean to say, we need to give the serverURL(database) to the
>> > reportviewer )
>> > but at my client place the web application is installed on one
>> > server(which is configured to public IP) and the database is on other
>> > server(which is not publicIP)
>> > So when i try to view the report from my web application i am getting
>> > error "page not Found"
>> >
>> > can any one please tell me the way to view the reports in my web page
>> > with other than reportviewer.. which gives the same functionality and
>> > which can overcome these sort of security issues
>> >
>> > thanx
>> > anil...
>> >
>> >
>
Wednesday, March 7, 2012
Is there any way to embed VB OCX control in SSRS ?
Thanks
I have read some articles and learnt that, at present, there is no support for custom controls. If anybody know any information on this please provide here.
Is there any way to control the visibility of items in Reporting Services Toolbar ?
thanks, ShyamThere are two ways of achieving this result:
1. if you use the VS 2005 report controls in server mode, you can turn on and off individual buttons in the toolbar. You can also override their default behavior.
2. if you use RS 2000 or RS 2005 out of the box, you can specify a custom stylesheet. You can customize each button individually by changing the stylesheet. There is some documentation in the readme about using custom stylesheets. Basically, you want to change the style display:inline to display:none for the items you don't want visible.
After you create the stylesheet, you can use it in one of two ways:
a. Use the rc:stylesheet property on your URL.
b. Modify the config file to treat your new stylesheet as the default for all reports.
Note that stylesheet support is not available in current SQL 2005 builds (it will be before RTM). Stylesheet support is in RS2000 (all releases) and I think the ability to change the default stylesheet was added in SP2.
Thanks
Tudor
|||Is stylesheet support available in the Sept CTP? I have been unsuccessful at implementing custom stylesheets using the documentation in the readme.|||Hello,
I'm facing with some related problem.
If i make something invisible (say a subreport) still, the report server fires the SP for that subreport. Is there anything in config file related to set this ? let me know !
Regards,
abhay
Could you possibly go into more detail how to go about turning on and off individual buttons through VS 2005 report controls in server mode?
Thanks!!
Is there any way to control the visibility of items in Reporting Services Toolbar ?
thanks, Shyam
There are two ways of achieving this result:
1. if you use the VS 2005 report controls in server mode, you can turn on and off individual buttons in the toolbar. You can also override their default behavior.
2. if you use RS 2000 or RS 2005 out of the box, you can specify a custom stylesheet. You can customize each button individually by changing the stylesheet. There is some documentation in the readme about using custom stylesheets. Basically, you want to change the style display:inline to display:none for the items you don't want visible.
After you create the stylesheet, you can use it in one of two ways:
a. Use the rc:stylesheet property on your URL.
b. Modify the config file to treat your new stylesheet as the default for all reports.
Note that stylesheet support is not available in current SQL 2005 builds (it will be before RTM). Stylesheet support is in RS2000 (all releases) and I think the ability to change the default stylesheet was added in SP2.
Thanks
Tudor
|||Is stylesheet support available in the Sept CTP? I have been unsuccessful at implementing custom stylesheets using the documentation in the readme.|||Hello,
I'm facing with some related problem.
If i make something invisible (say a subreport) still, the report server fires the SP for that subreport. Is there anything in config file related to set this ? let me know !
Regards,
abhay
Could you possibly go into more detail how to go about turning on and off individual buttons through VS 2005 report controls in server mode?
Thanks!!
Is there any way to control the visibility of items in Reporting Services Toolbar ?
thanks, Shyam
There are two ways of achieving this result:
1. if you use the VS 2005 report controls in server mode, you can turn on and off individual buttons in the toolbar. You can also override their default behavior.
2. if you use RS 2000 or RS 2005 out of the box, you can specify a custom stylesheet. You can customize each button individually by changing the stylesheet. There is some documentation in the readme about using custom stylesheets. Basically, you want to change the style display:inline to display:none for the items you don't want visible.
After you create the stylesheet, you can use it in one of two ways:
a. Use the rc:stylesheet property on your URL.
b. Modify the config file to treat your new stylesheet as the default for all reports.
Note that stylesheet support is not available in current SQL 2005 builds (it will be before RTM). Stylesheet support is in RS2000 (all releases) and I think the ability to change the default stylesheet was added in SP2.
Thanks
Tudor
|||Is stylesheet support available in the Sept CTP? I have been unsuccessful at implementing custom stylesheets using the documentation in the readme.|||Hello,
I'm facing with some related problem.
If i make something invisible (say a subreport) still, the report server fires the SP for that subreport. Is there anything in config file related to set this ? let me know !
Regards,
abhay
Could you possibly go into more detail how to go about turning on and off individual buttons through VS 2005 report controls in server mode?
Thanks!!
Is there any way of keeping all of a solution in one script project?
We do not have a source code control plug in for Visual Studio 2005 and I am trying to establish an efficient way of controlling versions of a solution I have created in BIDS, which includes SSAS objects plus an SSIS package.
As there are so many individual files for the dimensions, cubes, database, etc., it does not seem feasible to have them all checked in to our source control application and I was thinking of creating an Analysis Services Scripts project via SQL Server Mgt Studio where I could simply script out the SSAS database and the package and use these via the Deployment Wizard to deploy.
However -
a) according to BOL, an Analysis Services Scripts project has Connections, Scripts and Miscellaneous folders - when I create one, it has Queries instead of Scripts and when I script out the database I cannot see the xmla file in the project. Am I getting hold of the wrong end of the stick here?!
b) An SSIS package cannoy, I think, be scripted as such; when you deploy it creates the dtsx file and the SSIS DeploymentManifest file that installs the package, so is the best idea to keep these two files in source control?
Any advice gratefully received! Thank you
Rachel
I am a little bit surprised that your source control system has a limitation on number of files that affects you. In typical project you might have couple of dozen files, let's say up to a hundrend in a big solution - but modern source control systems can handle hundrends of thousands of files. Is there something here that I miss ?|||In Visual Source Safe, part of Visual Studio, you do not check in and out individual files, only objects like dimensions and cubes.
Are you trying to build your own version control system? Visual Source Safe should be enough for projects with 1-5 developers?
Regards
Thomas Ivarsson
|||Sorry, I was not making myself clear; we use MKS Source Integrity (a rather old version that does not integrate with VS) and there is no limit to the number of files it can deal with, but when I started checking in all the dim, cube, dsv, database, ds, dwproj, sln files etc it became apparent that it would be difficult to manage in that you would need to know which files would be affected by a change before you made it - I ended up checking everything out every time (a waste of time and effort!).
So I thought one script file for the database plus whatever the relevant files for the SSIS package are might be a better way forward, but would appreciate advice.
|||If only we had VSS! (see my response to Mosha above)|||So...any further advice from anyone?