Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Our <a href="http://www.datadynamics.com/Products/DDRPT/Default.aspx" rel="nofollow noreferrer">Data Dynamics Reports product</a> sound like it is for you. It is a fully programmable reporting component for .NET / Visual Studio. View the documentation on the API <a href="http://www.datadynamics.com/Help/ddReports/webframe.html" rel="nofollow noreferrer">here</a>. You can export the reports to any of our various formats, including PDF, HTML, and Excel and it also includes an end user designer control that you can embed into your own applications to let end users modify or create their own reports. </p> <p>The reports are stored in RDL - the same XML dialect that Reporting Services uses - in fact you can take any existing RDL files and open them in Data Dynamics Reports. In addition to compatibility with RDL, we add many more features, such as "themes" to consistently style your report, <a href="http://www.datadynamics.com/Products/DDRPT/ScreencastViewer.aspx?ID=MASTR" rel="nofollow noreferrer">master reports</a> (think ASP.NET master pages for reports), and several other built in controls such as a calendar, barcode, and <a href="http://www.datadynamics.com/Products/DDRPT/ScreencastViewer.aspx?ID=DSHBD" rel="nofollow noreferrer">dashboard controls</a> to name a few.</p> <p>Now lets look at your requirements one-by-one and see how Data Dynamics Reports might solve them:</p> <ul> <li>be invoked through code (not interactively) - <strong>Data Dynamics Reports includes comprehensive API.</strong> </li> <li>run on Windows, ideally invoked from code within a web-server - <strong>You can use Data Dynamics Reports in client-based, or ASP.NET applications, it even support medium trust ASP.NET applications (webservices are fine).</strong></li> <li>process standalone* report files that contain their own internal data definitions, query options, etc (i.e. ideally so that we can push simple report files to the server, and it simply work - where report/document maintenance is not necessarily a developer activity) - <strong>Data Dynamics Reports uses standard RDL (not rdlc) which includes all information bout how to retrieve data from your datasource. We also include an end user designer control to allow you to emebed a design environment for these standalone files into your own applications.</strong></li> <li>access data from a database (SQL Server 2005) based on parameters (ids etc) that we pass in - <strong>Data Dynamics Reports includes comprehensive support for parameters (even get the "valid values" from a query.</strong></li> <li>export (again, through code) to pdf or similar - <strong>Data Dynamics Reports supports exporting to PDF, HTML, Excel, Word, images, and XML.</strong></li> </ul> <p>I hope it works out for you, and let me know if you have any additional questions.</p> <pre><code>Scott Willeke Data Dynamics / GrapeCity inc. </code></pre>
 

Querying!

 
Guidance

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