My requirement was to add a text box along with the button to refresh the report. when user put some integer value in the text box and hit the button the data should be refreshed by using that integer value as filter (where clause in the query (variable: qry here).

Since the rvwMain.LocalReport.DataSources is a collection the report implicitly takes the first added source as the source to refresh the report in subsequent button clicks.

To resolve this issue I just cleared the DataSources collection of the LocalReport to get the desired result.
Here is how to do it.

rvwMain.LocalReport.DataSources.Clear();
rvwMain.LocalReport.DataSources.Add(…);

Just thought share it with everyone hoping that it might help the readers.

Thanks,
Kritul

“Depending on what sections the user wants to see, I cut out the unwanted sections and adjust the elements based on the cumulative elements. Be careful: the report designer usually removes the element for the top-most control (when it’s located at position 0,0) and the element for the bottom-most control.”

It should have been (with angle brackets around Top and Height):

“Depending on what sections the user wants to see, I cut out the unwanted sections and adjust the Top elements based on the cumulative Height elements. Be careful: the report designer usually removes the Top element for the top-most control (when it’s located at position 0,0) and the Height element for the bottom-most control.”

Also, set the BorderStyle to None for the rectangle controls (report sections).

When you have multiple datasets(really just tables), you need to be able to distinguish fields from them. With tables/matrices/lists there is a property DataSetName that you can set to the name of your dataset. Be careful, the Report Designed sometimes obliterates this property when you add new datasets. For textboxes, you have to use the First function where the first argument is the Fields!.Value and the second argument is the name of the dataset, e.g., =First(Fields!City.Value, “VendorList_Vendors”).

When you want to have dynamic control values in the header/footer regions, you can’t reference dataset fields directly. Most folks put secondary controls in the report body, tie them to the dataset fields, hide them and then tie the header/footer controls to the hidden ones in the body.

That’s sort of sloppy and I’ve heard it doesn’t always work properly. A better way is to directly manipulate the xml in the rdl/rdlc files and then calling the the LoadReportDefinition method like so: b. viewer.LocalReport.LoadReportDefinition(new MemoryStream( System.Text.ASCIIEncoding.ASCII.GetBytes(xDoc.InnerXml))); where xDoc is an XmlDocument object with the modified rdlc xml.

When it comes to dynamic images in the the header/footer, a good way to achieve this is to add dummy embedded images to the report and point your header/footer image controls to the embedded images. Once again, you modify the value of the embedded images in the rdlc xml prior to loading the report definition in the viewer. Here’s a method:

public void SetHeaderImage(XmlDocument xDoc, string name, byte[] imgData, string format)
{
XmlElement elem = null;
XmlNode img = SelectSingleNode(xDoc.ChildNodes[1], “//Report/EmbeddedImages/EmbeddedImage[@Name='" + name + "']“);
if (img != null)
{
elem = (XmlElement)SelectSingleNode(img, “./MIMEType”);
elem.InnerText = format;
elem = (XmlElement)SelectSingleNode(img, “./ImageData”);
elem.InnerText = Convert.ToBase64String(imgData);
}
}

and here’s a helper method for selecting the right node:

public XmlNode SelectSingleNode(XmlNode start, string path)
{
XmlNamespaceManager nsmgr = new XmlNamespaceManager(start.OwnerDocument.NameTable);
nsmgr.AddNamespace(“rptDef”, “http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition”);
if (path.StartsWith(“//”))
path = “/” + path.Substring(1).Replace(“/”, “/rptDef:”);
else if (path.StartsWith(“.//”))
path = “./” + path.Substring(2).Replace(“/”, “/rptDef:”);
else
path = path.Replace(“/”, “/rptDef:”);

XmlNode node = start.SelectSingleNode(path, nsmgr);
return node;
}

Now you can have truly dynamic headers/footers.

For optional report sections, many folks use subreports, but I’ve heard that can be slow. Instead, I put all of my report sections inside Rectangle controls in the report body and manipulate the xml once again. Depending on what sections the user wants to see, I cut out the unwanted sections and adjust the elements based on the cumulative elements. Be careful: the report designer usually removes the element for the top-most control (when it’s located at position 0,0) and the element for the bottom-most control.

I hope this helps out some folks who want to do some cool stuff with client-side RS reporting.

Cheers!

Now for a leisurely afternoon creating stored procedures and report templates, rather than a frustrated afternoon trying to understand the MSDN

¿¿podrías poner la solución??

Gracias.