Problem: Certain report items are not showing up in the toolbox in Visual Studio.
Solution: Right-click the toolbox, select Add/Remove Items (Choose Items in Visual Studio 2005) and click the Reset button.
Problem: Report files open as XML in Visual Studio.
Cause: Data Dynamics Reports was installed by someone other than the machine administrator.
Solution: Reinstall Data Dynamics Reports as the machine administrator. Select "For All Users" so that restricted users can access reports in Visual Studio.
Problem: When trying to create or open Web projects with Data Dynamics Reports, there is an error "Not a member of VS Developers group on the Web server computer."
Solution: Add the restricted user to the VS Developers group on the machine.
Problem: With a group of textboxes to the left or right of a table (one or more below the table's bottom edge) at run time the lower textboxes are pushed down below the expanded table while the upper textboxes remain where you placed them at design time.
Solution: Place the group of textboxes within a rectangle.
Problem: Setting the PageBreakAtEnd property of the List data region does not cause the report to break to a new page until all of the data in the list has rendered. How can I cause the report to break to a new page for each new record?
Solution: Add a Detail Grouping to the list and set the PageBreakAtEnd property of the grouping.
Problem: An expression using a numeric field name does not display any data at run time.
i.e. =Fields!2004.Value
Cause: Visual Basic syntax does not allow an identifier that begins with a number.
Solution: Make the numeric field name a string.
i.e. =Fields("2004").Value
or =Fields.Item("2004").Value
Problem: After installing a new build, opening a Windows Application that has the ReportPreview control generates a lot of errors.
Solution: Go to the Project Properties, and on the References page, select each of the DataDynamics.Reports.* references in turn and change the Specific Version property of each one to False.
Web Troubleshooting
Problem: The WebReportViewer shows an "Error Creating Control" message on the WebForm instead of the control after installing a new build.
Solution: Manually update the version number.
- Open the WebForm on which you have the viewer and click the HTML page at the bottom to go to the HTML view.
- Change the version number in the @ Register directive block (<%@ Register ... %>) in the yellow area at the top to match that of the installed build.
- Close and save the WebForm.
- Open the CoreHandler.ashx file that is automatically added to the solution when you use the WebReportViewer.
- Change the version number to match that of the installed build.
- Close and save CoreHandler.ashx.
Problem: In Visual Studio 2005, dropping a WebReportViewer control onto a WebForm does not add a reference to DataDynamics.Reports.Web.
Solution: Manually add the reference.
Problem: When you set the Dock property to True, the WebReportViewer only docks to the top and sides of the WebForm. At run time, when you maximize the browser, there is a large empty space at the bottom of the page and you have to scroll to see the report in the top half.
Cause: After you have added and deleted Data Dynamics Reports Web controls and updated versions, sometimes there is an extra @ Register directive block (<%@ Register ... %>) left behind in the HTML view of the ASPX.
Solution: Go to the HTML view of the ASPX page containing the WebReportViewer control and, in the yellow section at the top, look for an extra @ Register directive block with a TagPrefix value like "dd:1" and delete the entire line (from <% to %>).
Problem: The WebReportViewer does not show up correctly in FireFox (or Konqueror, or Opera, or AppleWebKit-based browsers like Safari, or Gecko-based browsers like Netscape or Mozilla).
Solution: Manually add the following BrowserCaps code to the Web.config file just below the <system.web> tag.
<browserCaps> <!-- Name: BrowserCaps update for modern browsers, http://slingfive.com/pages/code/browserCaps/ Author: Rob Eberhardt, http://slingfive.com/ History: 2004-11-19 improved detection of Safari, Konqueror and Mozilla variants, added Opera detection 2003-12-21 updated TagWriter info 2003-12-03 first published --> <!-- GECKO Based Browsers (Netscape 6+, Mozilla/Firefox, ...) //--> <CASE match="^Mozilla/5\.0 \([^)]*\) (Gecko/[-\d]+)(?'VendorProductToken' (?'type'[^/\d]*)([\d]*)/(?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*)))?"> browser=Gecko <FILTER> <CASE match="(Gecko/[-\d]+)(?'VendorProductToken' (?'type'[^/\d]*)([\d]*)/(?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*)))"> type=${type} </CASE> <CASE><!-- plain Mozilla if no VendorProductToken found --> type=Mozilla </CASE> </FILTER> frames=true tables=true cookies=true javascript=true javaapplets=true ecmascriptversion=1.5 w3cdomversion=1.0 css1=true css2=true xml=true tagwriter=System.Web.UI.HtmlTextWriter <CASE match="rv:(?'version'(?'major'\d+)(?'minor'\.\d+)(?'letters'\w*))"> version=${version} majorversion=0${major} minorversion=0${minor} <CASE match="^b" with="${letters}"> beta=true </CASE> </CASE> </CASE> <!-- AppleWebKit Based Browsers (Safari...) //--> <CASE match="AppleWebKit/(?'version'(?'major'\d?)(?'minor'\d{2})(?'letters'\w*)?)"> browser=AppleWebKit version=${version} majorversion=0${major} minorversion=0.${minor} frames=true tables=true cookies=true javascript=true javaapplets=true ecmascriptversion=1.5 w3cdomversion=1.0 css1=true css2=true xml=true tagwriter=System.Web.UI.HtmlTextWriter <CASE match="AppleWebKit/(?'version'(?'major'\d)(?'minor'\d+)(?'letters'\w*))(.* )?(?'type'[^/\d]*)/.*( |$)"> type=${type} </CASE> </CASE> <!-- Konqueror //--> <CASE match=".+[K|k]onqueror/(?'version'(?'major'\d+)(?'minor'(\.[\d])*)(?'letters'[^;]*));\s+(?'platform'[^;\)]*)(;|\))"> browser=Konqueror version=${version} majorversion=0${major} minorversion=0${minor} platform=${platform} type=Konqueror frames=true tables=true cookies=true javascript=true javaapplets=true ecmascriptversion=1.5 w3cdomversion=1.0 css1=true css2=true xml=true tagwriter=System.Web.UI.HtmlTextWriter </CASE> <!-- Opera //--> <CASE match="Opera[ /](?'version'(?'major'\d+)(?'minor'\.(?'minorint'\d+))(?'letters'\w*))"> <FILTER match="[7-9]" with="${major}"> tagwriter=System.Web.UI.HtmlTextWriter </FILTER> <FILTER> <CASE match="7" with="${major}"> <FILTER> <CASE match="[5-9]" with="${minorint}"> ecmascriptversion=1.5 </CASE> <CASE> ecmascriptversion=1.4 </CASE> </FILTER> </CASE> <CASE match="[8-9]" with="${major}"> ecmascriptversion=1.5 </CASE> </FILTER> </CASE> </browserCaps>
![]() |
Tip: If you have a problem that is not listed here, you may find the solution in the Forums. |
Show or hide BrowserCaps code