Databases
StackOverflow2013
Postsdbo
POReportViewer problems
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POReportViewer problems
    primarykey
    data
    text
    <p>I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation. </p> <p>I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server. </p> <p>I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.</p> <p>So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue</p> <p>So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:</p> <p>Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.</p> <p>The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.</p> <p>I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.</p> <p>Any help would be appreciated</p> <p>Thanks,</p> <p>Doug</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDoug Ingham
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COAre you using a wizard to create report? Wizard messes things up. Also, have you added `using System.Windows.Forms;`
      singulars
      1. POReportViewer problems
      1. USShruti Kapoor
    2. COAlso, have you included `using Microsoft.Reporting.WinForms;`
      singulars
      1. POReportViewer problems
      1. USShruti Kapoor
    3. COI've tried checking the namespace Microsoft.Reporting.Winform. Errors went away after that, but when I rebuilt, the errors came back.
      singulars
      1. POReportViewer problems
      1. USDoug Ingham
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload