Parameter's of report get refreshed in report viewer

  • Hi All,

    I had developed a C# windows application using .Net 2008 and SQL server 2008 (developer edition). I had XP operating system. I had used ReportViewer (version 9.0) controls in one of the forms. I had created an installer for the same and installed it on my machine as well as other xp machine. Everything worked fine. I was able to view the reports and export the reports to excel.

    Eventually my machine was upgraded to Windows 7 and I had .Net 2010 installed with same SQL 2008. Now when we opened the form to make changes, the report viewer was no longer supported since there was a new version 10.0 for the same. When I dragged a report viewer control to the form it started giving me error. I resolved it by dropping the form and creating a new form with the new report viewer (10.0) and created a new setup again for the same. It worked fine on my machine (windows 7).

    In the C# (.csproj) and Setup (.vdproj) there were references of ReportViewer 9.0. So I thought creating new form and new setup would definitely help.

    When I installed this setup on the other XP machine there was a problem. The problem is, whenever we click on the report viewer’s view button the parameters get refreshed. There is a startdate, enddate (datetimepicker) and employee dropdown on the report viewer for a report.

    The Startdate and Enddate have default values 1st date of month and last date of the month respectively out of which later is not displayed. If we select last date and an employee and click view report the enddate and employee boxes are refreshed out and we are unable to see report.

    Using report manager there is no problem viewing the report nor are the parameters refreshed there.

    Please let me know what exactly is causing this issue.

  • Team,

    I have found a solution for the same. I installed Microsoft ReportViewer 2010 Redistributable Setup on target machine and it solved the problem for me.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply