We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ...
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.
1) Create an external Assembly DLL (Class Library). You can use Framework 3.5.
a) Name it ‘DataForSSRSReport’.
b) Rename the default class to ‘clsDataForSSRS’. Make sure the class is Public.
c) Use ‘Private Shared’, ‘Public Shared Property’, and ‘Public Shared …
In the ActiveReport-ReportStart section of your parent report, you can assign any object type to the Report object variable, ‘UserData’
UserData is a public object of the DataDynamics.ActiveReports.ActiveReport.
Scenario:
Let’s say you are using a Watermark in your parent report. …
If you are like me and have a report that dynamically calls a sub report that then calls sub reports (using the sub report control), you may have run into the occasional sub report overlap nightmare. The latest encounter for …
Instead of passing a parameter to a report with a value set to preexisting data, you can instead prompt the user running the report with an inputBox (Microsoft.VisualBasic) in order to capture the data on the fly to be used …