November 5, 2008 at 6:02 am
Hi,
I have a report in Report server.
There are three client application accessing the same report and using report viewer control for display purpose.
Now all three application shows same data.
I need to modify my asp.net (C#) code or report to work based on the calling application and display of their own.
Please advice me how to proceed further.
If you are not clear on my description please let me know.
PS: All three application DB structure are same, used by different clients.
Thanks,
Sundar
November 5, 2008 at 3:54 pm
Do you mean that each user will supply a different report parameter that would cause their respective reports to differ?
If they shouldn't receive the identical report, what would cause the reports to be different?
Perhaps the report is being cached? If so, you can set a report property that will prevent caching and cause a fresh execution each time the report is called.
November 5, 2008 at 9:34 pm
No not like that.
Each report needs to retrive data from different database. (But all Database structure are same, so the same stored procedure is available in all DB's)
SAy for example:
Appln A , Appln B & Appln C - all are calling the same RS report with same parameters.
When ApplnA calls the report then our RS report need to connect to Appln A's DB (i.e. DB A) and retrive data.
Currently All three applications are getting DB A's data, not their own data.
How to achive this ?
November 6, 2008 at 6:58 am
You would need to change the Data Source of the report. I haven't done this, but it looks like there are a couple of ways it can be done. See this thread:
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1255157&SiteID=1
November 6, 2008 at 7:40 am
I agree, we have reports that change Data source (SQL Server name) at runtime, when you pick the Server Name from a dropdown list
November 6, 2008 at 11:00 am
Try not to hardcode data source......
http://www.sqlservercentral.com/articles/Development/2945/
this is a tutorial..
Sayed
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply