User talk:Perpetuum Software Team
From Wikipedia, the free encyclopedia
[edit] Reporting tools comparison
A proposed deletion template has been added to the article Reporting tools comparison, suggesting that it be deleted according to the proposed deletion process. All contributions are appreciated, but this article may not satisfy Wikipedia's criteria for inclusion, and the deletion notice should explain why (see also "What Wikipedia is not" and Wikipedia's deletion policy). You may prevent the proposed deletion by removing the {{dated prod}} notice, but please explain why you disagree with the proposed deletion in your edit summary or on its talk page. Also, please consider improving the article to address the issues raised. Even though removing the deletion notice will prevent deletion through the proposed deletion process, the article may still be deleted if it matches any of the speedy deletion criteria or it can be sent to Articles for Deletion, where it may be deleted if consensus to delete is reached. If you agree with the deletion of the article, and you are the only person who has made substantial edits to the page, please add {{db-author}} to the top of Reporting tools comparison. Gromlakh (talk) 08:33, 30 January 2008 (UTC)
[edit] Speedy deletion of Automatic synchronization of two database schemas
A tag has been placed on Automatic synchronization of two database schemas requesting that it be speedily deleted from Wikipedia. This has been done under section G12 of the criteria for speedy deletion, because the article appears to be a blatant copyrightinfringement. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material, and as a consequence, your addition will most likely be deleted. You may use external websites as a source of information, but not as a source of sentences. This part is crucial: say it in your own words.
If the external website belongs to you, and you want to allow Wikipedia to use the text — which means allowing other people to modify it — then you must include on the external site the statement "I, (name), am the author of this article, (article name), and I release its content under the terms of the GNU Free Documentation License, Version 1.2 and later." You might want to look at Wikipedia's policies and guidelines for more details, or ask a question here.
If you think that this notice was placed here in error, you may contest the deletion by adding {{hangon}} to the top of the page (just below the existing speedy deletion or "db" tag), coupled with adding a note on the article's talk page explaining your position, but be aware that once tagged for speedy deletion, if the article meets the criterion it may be deleted without delay. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the article that would would render it more in conformance with Wikipedia's policies and guidelines. Gromlakh (talk) 08:40, 30 January 2008 (UTC)
| .NET WinForms | ActiveReports for .NET Professional V3.0 | ActiveReports for .NET Standard V3.0 | Data Dynamics Reports 1.0 | XtraReports 7.2 | Report Sharp Shooter 3.5 | Teleric Reporting Q2 2007 | Microsoft ReportViewer (Integrated in VS2005) | |
|---|---|---|---|---|---|---|---|---|
| Product Features Count | ||||||||
| Report Design Features | ||||||||
| Crystal Reports Compatible | • | • | • | • | • | Generally this means the ability to use report structures produced with Crystal Reports | ||
| User Designer Control | • | • | • | • | • | Allows the End User (viewer of the report) access to the report's design | ||
| Developer Design Wizard | • | • | • | • | • | • | Wizard to facilitate the design of reports | |
| Table Support | • | • | • | • | • | Allows report authors to easily group report items in a tabular format | ||
| List Support | • | • | • | • | • | • | • | Allows report authors to aggregate data and output that at the detail level |
| Detail Grouping | • | • | • | • | • | • | • | Allows repetitions of a report on a page, can be used to generate labels |
| Label Support | • | • | • | • | • | • | • | Allows repetitions of a report on a page, can be used to generate labels |
| Object Reusability | • | • | • | • | • | • | • | Allows a report designer to reuse sections of the report layout in other areas of the report, or other reports |
| Multiple reporting 'bands' on a page | • | • | • | • | • | • | • | Sectioning of report data on a page. Allows multi-origin report outputs to be displayed at the same level. |
| Final Report Modification | • | • | • | • | Allows modification of the final report output (once produced) using the Report Designer component, allowing fine-tuning of the presentation | |||
| Multi-column reports | • | • | • | • | • | • | • | Allows the generation of multi-column reports (multiple columns on one page). |
| Thin Client Interface | • | • | • | • | • | No space is taken up client side when a user interacts with the reporting component. This means all data processing and report generation runs server side | ||
| MMC User Interface | Component methods and properties can be accessed from the Microsoft Management Console | |||||||
| Hyperlink Embedding | • | • | • | • | • | Allows the inclusion of Hyperlinks within a report, these can be used to provide Drill down, Roll up functionality, jump to Table Of Contents page, etc… | ||
| Component Embedding | • | • | • | • | • | • | Allows the inclusion of components within a report, this can
increase the functionality available in the end report. E.g. Addition of an email component allowing emailing of a report at the touch of a button |
|
| OLE Objects Embedding | • | • | • | • | • | • | Object Linking and Embedding support, this allows inclusion of BLOB (Binary Large Objects) in a report, e.g. Pictures, wave files, etc… | |
| Access / Excel Addins | Quickly and easily create presentation-quality reports from within a familiar Microsoft Access and Excel environment | |||||||
| Barcode font support | • | • | • | • | • | Report output can include barcode fonts | ||
| Native Barcode Support | • | • | • | • | • | Support Native Barcodes in the report design | ||
| 2D Barcode Support | • | • | • | Support 2D Barcodes in the report design | ||||
| Script Debugger | Opens an Script Debugger (JIT) when a scripting error occurs in event or expression related script | |||||||
| Automatic SQL generation | Builds SQL statements dynamically so the user never has to know anything about SQL. | |||||||
| Integrated C# and VB compilers | • | • | • | • | • | • | You can write C# and VB code from within the report designer, and it will be compiled and executed at runtime. This is a very powerful feature, enabling | |
| Add code in any .NET language | • | • | • | • | • | • | • | You can write add-ins in any language that can produce a .NET assembly, and reference that code from within your report. |
| Event Handlers | • | • | • | • | • | • | Allows a report designer to specify the functional result of an event, e.g. produce graph of sales figures on double-click event | |
| Scripting events / expressions | • | • | • | • | • | • | Allows the inclusion of Script
within a report, this can provide a way of including extra functionality dependant on events or expressions within the report |
|
| Data Callback Function | • | • | • | • | • | • | • | Allows a report designer to interface with custom code to process report data externally before rendering into the report |
| Unicode, Internationalization Support | • | • | • | • | • | • | • | Allows reports to contain characters that conform to the Unicode standard character set |
| Right-To-Left text support | • | • | • | • | Enables text to be entered in a right-to-left format for Arabic applications | |||
| Localization of the UI | • | • | • | • | • | • | • | Dialogs, forms, etc. can be displayed in different languages |
| CSS Property Editor | • | • | • | • | • | Control style property editor based on the Cascading StyleSheet (.css) syntax | ||
| Report Style sheet | • | • | • | • | • | • | Style Sheets for report style specification | |
| Full Reporting API | • | • | • | • | • | • | Every report can be generated independently from the Report Designer | |
| Integration with Visual Studio | • | • | • | • | • | • | • | Integration of the Report Designer with the development framework |
| Report Parameters | • | • | • | • | • | • | • | Parameters for a report are treated as first-class objects within the report |
| Cascading report parameters | • | • | A parameter's set of valid values can be determined by another parameter's value | |||||
| Hierarchical grouping | • | • | • | • | A group can have a parent that
is determined by another field at runtime (recursive grouping - group on employee id where the parent is the value of another |
|||
| Embedded Report Authentication | Report can be viewed and modified only with authentication | |||||||
| Calendar | A calendar can be easily created by the report author | |||||||
| Rich Text | • | • | • | • | • | • | • | A report can contain richly formatted text, that is text that can have different formatting applied to each word or character if needed |
| Extensible Report Items | • | New report items can be created using the SDK available with the product | ||||||
| Windows Forms Control host | • | • | • | Windows Forms controls can be hosted on a report opening up additional reporting opportinities | ||||
| Report inheritence | • | • | • | • | • | One report can serve as the basis for other reports with modifications taking affect on all child reports | ||
| Report Output Features | ||||||||
| Cross-Tab | • | • | • | • | Enables generation of Cross-Tab reports, e.g. Pivot Table | |||
| Drill-Down | • | • | • | • | • | • | Drill down on a selected item within a report allows
all or selected information to be displayed for a selected item of a report. Can be used in reverse as a grouping function |
|
| Roll-Up | • | • | • | Opposite of Drill down functionality, allows the user to view a grouped display for a selection of items within the report | ||||
| User Query Designer | • | • | Allows the End User (viewer of the report) to query the connected datasource within the bounds of certain parameters | |||||
| Graphing | • | • | • | • | • | • | • | Graphs can be produced from the data within a report |
| Print/Preview | • | • | • | • | • | • | • | Allows the user to preview a report and print the result of the preview |
| Field Print selection | • | • | • | • | • | Specific fields can be selected at design time to appear in the printed report | ||
| XSL support | • | • | Allows XML stylesheets to format the report display | |||||
| Layout Import / Export | • | • | • | • | • | • | • | Import or Export of report layout / structure so this can be transferred quickly between users - often stored as XML file type |
| Report Caching | • | • | • | • | • | • | Report pages are individually cached during generation, reducing waiting time before a report can be read | |
| Web Report Caching | • | • | • | • | • | • | Allows reports to be cached on a server, enabling very fast serving of these when next called for | |
| Navigation Bar | • | • | • | • | • | • | • | Navigation bar with scrolling / page selection to be included in the output (although not printed) report |
| Report Paging | • | • | • | • | • | • | • | Paged reports are produced allowing page selection / display to facilitate report viewing (page counting functionality) |
| Automatic Page Scrolling / Resizing | • | • | • | • | Determines whether the report should be presented as all on one page (resized to fit), or scroll bars should be added | |||
| Page overlays (alpha blending) | • | • | • | • | • | • | • | Watermark or background images can be included in the report |
| ToolTips | • | • | • | • | • | • | • | ToolTips available for objects / sections in the final report output |
| Layout based report | • | Multiple data areas can occupy the same vertical space in a report | ||||||
| Image output from a datasource | • | • | • | • | • | • | • | Take images from a database and output these in a report like data from any other field |
| Report merging | • | • | • | • | • | Take the output from two or more reports and combine them into a single report | ||
| Advanced page output support | • | • | Multiple pages in the report can be merged into one physical page, output pages in an order suitable for creating a folded booklet | |||||
| Data Visualizers | • | Built-in functionality to generate colors or images based on values in a report | ||||||
| Report Viewer Features | ||||||||
| ActiveX Proprietary Viewer | • | • | Client-side Report Viewer for ActiveX | |||||
| .NET Proprietary Viewer | • | • | • | • | • | • | • | Client-side Report Viewer for .NET (i.e. Win Forms) |
| ASP.NET Proprietary Viewer | • | • | • | • | • | • | • | Client-side Report Viewer for ASP.NET (i.e. Web Forms) |
| J2SE Proprietary Viewer | Client-side Report Viewer for J2SE | |||||||
| J2ME Proprietary Viewer | Client-side Report Viewer for J2ME | |||||||
| VCL Proprietary Viewer | Client-side Report Viewer for VCL | |||||||
| Report Parameters supported by the Viewer | • | The report viewer control provides a UI to enter parameter values | ||||||
| Report Export Features | &nb sp; | |||||||
| HTML | • | • | • | • | • | • | Export report data to HTML (Hyper Text Markup Language) | |
| XML | • | • | • | Export report data to XML (eXtensible Markup Language) | ||||
| • | • | • | • | • | • | • | Export report data to PDF (Portable Document Format) | |
| RTF | • | • | • | • | • | Export report data as Rich Text Format (RTF) | ||
| Word | • | • | Export report data as Microsoft Word format (so that the report reader can later edit the report) | |||||
| MHTML | • | • | • | • | Export report data as a MIME Encoded HTML Document (suitable for e-mailing) | |||
| Email (via internal MAPI) | • | • | Allows the report output to be emailed without end user involvement | |||||
| Proprietary File Type | • | • | • | • | • | • | A unique viewer is required in order to see the report output | |
| CSV | • | • | • | • | Data fields are separated by commas (Comma Separated Value) | |||
| XLS | • | • | • | • | • | Export report data to MS Excel format (XLS) | ||
| XHTML Mobile | Allows the report output to be viewed in mobile browser conforming to XHTML Mobile standard format | |||||||
| Text | • | • | • | • | Export Report data to Text file format | |||
| BMP | • | • | • | Standard windows format for storing images (Bit Map). Bit's per pixel level can be set to provide lossless, or lossy image storage | ||||
| GIF | • | • | • | (Graphics Interchange Format) One of the two most common file formats for images on the Internet | ||||
| JPEG | • | • | • | (Joint Photographic Experts Group) A common lossy image file format. Quality of compression can be specified | ||||
| Tiff | • | • | • | • | • | • | • | (Tag Image File Format) Commonly used raster image file format, often used in DTP applications |
| Vector Graphics format | • | Export data to Vector graphics format. Allows rescaling of the report with no loss of resolution | ||||||
| Extensible Rendering API | • | • | • | An API exists that would allow other developers to create their own rendering types (f.e. to add XPS output) | ||||
| DataSource Connection Type | ||||||||
| ADO.NET | • | • | • | • | • | • | • | ActiveX Data Objects for .NET from Microsoft allows
connection to relational and non-relational datasources from both Microsoft and other datasource providers, this is an expansion of the ADO connection type allowing greater interrelation connectivity |
| ADO | • | • | • | • | ActiveX Data Objects (and API) from Microsoft allows connection to relational and non-relational datasources from both Microsoft and other datasource providers | |||
| RDO | • | Remote Data Objects connection via Microsoft API (uses the lower level DAO as an actual connection) - now superseded by ADO | ||||||
| DAO | • | Data Access Objects connection - Microsoft's old standard database connection format, an API (now replaced by ADO) | ||||||
| XML | • | • | • | • | • | • | Allows connection to eXtensible Mark-up Language datasource | |
| OLAP | • | Allows connection to an Online Analytical Processing datasource (multidimensional datasource) - MDBMS compatible | ||||||
| Oracle | • | • | • | • | • | • | • | Allows connection to an Oracle database |
| Sybase | • | Allows connection to a Sybase database | ||||||
| Connectivity SDK | • | • | Separate SDK to enable the reporting application to bind to any database via API specified by the code produced by this SDK | |||||
| Unbound Data Support | • | • | • | • | • | • | • | Allows the report to be run on 'unbound' data - this is data that is not held on a connected datasource, it is held in the code native to the component |
| Control binding to data sets | • | • | • | • | • | • | • | Ability to bind all of the component's controls to a Data Set |
| Control Binding to system variables | • | • | Ability to bind all of the component's controls to a system's variables | |||||
| Native style Data Relations support | • | • | • | • | ADO.NET data structure
binding. Allows the parent (master) band to bind to a dataset's table, whilst the child (nested bands) bind to the child tables. This reduces the need for sub-reports |
|||
| .NET Enumerable Interface | • | • | • | • | • | • | Allows connection to any .NET object that supports enumerable interfaces (e.g. IList, ISourceList, Ienumerable) | |
| ODBC | • | • | • | • | • | Open Database Connectivity - allows SQL queries to be run on database. ODBC is included in ADO, RDO, DAO and ADO .NET | ||
| JDBC | Java Database Connectivity - allows SQL queries to be run on database. | |||||||
| SQL Query | • | • | • | • | • | • | • | Allows connection to SQL based databases such as Oracle |
| Legacy | Datasource type
that is a result of conversion from a unique programming language / format. Many large companies have Legacy forms of databases, these require careful interrogation to retrieve reportable data |
|||||||
| LDAP | Lightweight Directory Access Protocol, is a
protocol that enables a search to locate organizations, individuals, and other resources (such as files) in a network - whether intranet or internet |
|||||||
| J2EE Data Object | Allows direct interface with J2EE data object as data source | |||||||
| Multiple Datasource Reports | • | • | • | • | Reports can contain an unlimited number of datasources (database or user defined data source) | |||
| License Restrictions | ||||||||
| Royalty Free Report Designer Control | • | • | • | • | • | • | Allows developers to include a report design component in the distributed application without need to pay royalties for the distribution of this | |
| Source code available | • | • | • | Source code can be purchased for this product, allowing greater customization and flexibility |
