Tuesday, March 25, 2008

Query Reporter an easy-to-use freeware tool to create and run HTML reports from the results of a SQL query against an Oracle database

Query Reporter is an easy-to-use freeware tool to create and run HTML reports from the results of a SQL query against an Oracle database. From a simple query, you can define tabular, break, and master/detail reports. You can refine the layout by specifying colors, fonts, alignment, formats, sums, headers, backround, margins and so on. Major Query Reporter features Powerful substitution variables You can use substitution variables in the SQL text where input from the end-user is required. You can define if these substitution variables are string, number or date values, if they should be represented as selection lists or checkboxes, what the default value is, and so on. Substitution Variables Graphical Query Builder The graphical Query Builder makes it easy to create new select statements or modify existing ones. Just drag and drop tables and views, select columns for the field list, where clause and order by clause, join tables based on foreign key constraint definitions, and you're done. The Query Builder SQL Editor The SQL editor uses syntax highlighting to improve readability of the SQL text, and to quickly verify if your SQL syntax is correct. In case of an SQL syntax error, the cursor will be located on the error position. PL/SQL Developer report compatibility Query Reporter uses the same report definition file format as PL/SQL Developer. Therefore you can use Query Reporter to run reports created by PL/SQL Developer users, without needing a PL/SQL Developer license or installation. Command-line interface You can use Query Reporter's command-line interface to run reports without any user-interaction, and to save the result in an HTML file. These result files can be viewed with any Web Browser. For example: QueryReporter userid=scott/tiger@chicago exec=DeptEmp.rep html=DeptEmp.html quit Security You can create reports that need to be run under privileged accounts, without providing the password to the end-user.

http://intellect.dk/post/ActiveRecord-introduction.aspx

If you are using Borland's Delphi or C++Builder to develop Oracle applications, then the Direct Oracle Access component set can help you to make a seamless integration between this great development tool and database system. Not only will your application take maximum advantage of both products, your application development process will also benefit from the following key features: High performance Both online transaction and batch processing applications can benefit from Oracle's performance features. Direct Oracle Access, as the name suggests, directly accesses the Oracle Interface. This guarantees optimal performance for standard database access functions. Support for Array Fetching, Array DML, PL/SQL Blocks, PL/SQL Tables, Local Statement Caching and the Direct Path Load Engine enable you to optimize your application's performance critical functions even more. Easy application distribution A Direct Oracle Access application does not require middleware like the BDE or ODBC, it merely requires Oracle SQL*Net or Net8. Consequently you can deploy your application without many of the version dependency or configuration problems typically involved with middleware installation. Application distribution Oracle Package support Most PL/SQL code in Oracle databases is programmed in packages. Direct Oracle Access provides a TOraclePackage component that allows you to easily call packaged program units without detailed declarations of these program units and their parameters. Furthermore Direct Oracle Access includes a Package Wizard that can generate classes to encapsulate the program units and record types defined in packages. This will make your Oracle packages a natural extension of the Object Pascal or C++ language. The Package Wizard TOracleDataSet The dataset component in Direct Oracle Access supports Oracle record locking, record refreshing, server generated values, automatic sequence value generation, and BLOB compression

No comments: