How DatabaseAce Works
Point the REIGNN Maker at an external database (Oracle, SQLServer, MySQL Enterprise, PostgreSQL, Firebird or Interbase). The Maker generates a XML-based model of the database, which can then easily be customized by administrators to meet their specific business needs. DatabaseAce then reads the XML model at runtime to obtain instructions on how to produce a powerful and intuitive web interface customized to work with that database.
At left is an example of a XML file produced by the REIGNN Maker. Each file represents a single table in the underlying database. Administrators use these files to determine how (and if) each field should be displayed and validated. Foreign keys are represented as <relation> tags in the XML while child lists are represented as <list> tags. Many-to-many lists are shown as <junction> tags. All remaining columns are shown as <column> tags. A wide variety of attribute tags may be passed to column, relation, list and junction tags to customize their behavior.
At runtime, DatabaseAce parses the XML model and generates a web interface based on its contents. Each item in the menu on the left (in the screenshot) represents a table in the underlying database and is given its own area in the interface. The screenshot shows the main interface for a table named Items; all other tables use identical interfaces. The central feature of each table (as shown in the screenshot) is a list of records that allows users to paginate through the dataset in a conventional manner and also to export the data to PDF, Excel, SQL or CSV.
The screenshot at left shows an open Item record. Note that its relation to the Product table is represented as a dropdown. Products shown in the dropdown can be edited, deleted and added in a drill-down fashion by using the three small buttons to the right of the dropdown. Users may drill down for as many levels as the schema will allow. Files and images are handled through the file upload mechanism shown in the screenshot. Long text fields (like the Notes field) can be easily designated as such in the XML.
Child lists are displayed inside their parent. Shown here is a list of Item records inside a parent Product record. Note that the same interface is used to display items here as under the main Item menu, but this list contains only those items that belong to the Dogs category. Items can be opened from inside products, and products can be opened from inside items. Users can move through the schema in any direction through the conduits defined by the database's declared constraints.
Many-to-many relationships are represented as junction tags in the XML and are rendered in the interface as shown at left. Junctions allow records to be passed back and forth between two tables via an intermediary bridge table. New records can be added to the target table and existing records can be modified or removed.
Each table contains a filtering tool used to zero in on precise datasets. DatabaseAce employs high-powered nested boolean filters that allow for any number of specific search criteria to be strung together and/or nested inside each other ad infinitum. Filters can be saved and shared with other users; they are used both for searching data in its raw list form and for customizing the underlying datasets used to produce charts and exports.
Each table also includes an angling mechanism, which allow users to choose which columns to use and the order in which those columns should be displayed and sorted. In addition to standard record values, angles may include literal values, calculated values and concatenated values. When placed in aggregate mode, the angling mechanism can also use aggregations to find the count, sum, average, minimum or maximum values from within groups of records defined by sharing a common value. Like filters, angles can be saved for later use and/or shared with other users.
A table's vertical mechanism allows admins to visually carry out highly specific mass changes to one or more columns with the click of a button. A single column can be assigned either a literal value or can be synchronized with another column across all records in the current dataset. Previously saved filters can be applied to narrow the dataset before execution. LIke filters and angles, verticals can save the expense and tedious labor involved in manually updating large number of records. Verticals can also be saved for future use and/or shared with other users.
10  Each table's is equipped with a charting mechanism that brings data to life using visually stunning Flash-based charts. Chart the columns and calculations defined by previously saved angles against the datasets defined by previously saved filters. Choose from a wide selection of chart types, effects and other display options to fine-tune each chart's appearance, then save it for future use and/or share it with other users. The flexibility of the angles and filters on which charts are based makes them capable of rendering nearly any conceivable metric that is derivable from the underlying dataset.
11  DatabaseAce is fully skinnable; its layout and appearance can be customized to integrate seamlessly with your company website's existing colors and visual theme. In addition to the program's appearance, skins also control the appearance of PDF and Excel exports and charts. DatabaseAce can create a custom skin for you, or you can create one for your own organization. The image at right shows the same chart rendered using four different skins.
12  DatabaseAce's functional behavior is fully customizable. Automated fulfillment actions (such as sending personalized emails, pinging HTTP gateways, executing local scripts and uploading files) can be configured to take place in response to pre-defined trigger events such as 'record inserted,' 'record updated' or 'record deleted.' Mold the program's functionality to meet your precise requirements. When built-in fulfillments are insufficient to the task, custom fulfillment routines can be created and integrated seamlessly into DatabaseAce's interface.
Download
Tour
More Info
Buy