|
FullRecord stores the database operations of your system in one audit file:
| • | It can records the operations from any kind of file (ISAM, SQL (*), even IMDD if needed). |
| • | It can also records any manual hallmark you want to add (like "Special button pressed", or "Entered this particular procedure", even local variables or special events) |
| • | It is compatible with the Clarion IPDriver. |
| • | The auditing file may be ISAM or SQL (SQL currently tested with Pervasive SQL, SQL Anywhere, MS-SQL Server, ODBC-MySQL and ODBC-FIREBIRD). SQL storing supports server-side autonumbering. |
| • | There is only ONE main file for auditing storage. |
| • | Option to compress the audit data, to save disk space used by the Audit file. |
| • | Minimal local code is generated in your procedures. This makes your audit system COMPACT! |
| • | No decisions are made at the moment of recording, and only one record is stored per operation in FullRecord mode (no matter how many fields changed). The only exception is if you change the primary key, then two records are saved (This is to enable FullRecord to locate the original information). This makes your audit system FAST! |
| • | As an alternative from FullRecord 3.0 on, you can store the changed fields only. |
| • | Examine the audited data in functional ways: |
"Field" inspect window (to see the history of a particular field),
"Record" inspect window (to see the history of a particular record) and
General Audit Browse.
| • | You can undelete a deleted record or recover a changed record. |
| • | When you recover a deleted record that was replaced with new data, you may choose to overwrite the new data or renumber the old record to add it to the end of the file. |
| • | The FullRecord Global Template has "basic" and "advanced" options. In the Basic mode some of the complexity is hidden from the developer and it's ok if you set with the defaults. When you select the advanced option you have the ability to customize FullRecord to the maximum. |
FullRecord supports all the regular field types, as well as the auditing and recovering of files with:
| • | Memo fields (unlimited quantity) |
| • | Dimensioned fields (up to 4 dimensions). |
| • | Dimensioned GROUP fields |
(*) SQL back-end operations like cascade-engine updates and stored procedures cannot be audited, as they are out of the scope of the Clarion program.
|