Stored Report Maintenance
Reference Contents > Advanced Functions > Stored Report Maintenance
The Stored Report Destination exploits a capability of the system to create an internal binary image of a report before passing that to a devise that will in turn pass it to a physical printing device or file format. It is in effect a low-level definition of the report’s output. When you chose the Stored report destination the output of the report subsequently printed is captured (along with other data that would have been used for an email at the time, for example). This is then made available to be stored in the database along with a subject, comments and privileges settings so that it can be re-printed in the future.
When a report is printed to the Stored report destination the Stored Report Setup window is presented to the user in which additional data can be added and privileges for others selected. The user can then save the results to the database or abandon that by closing the window.
After creating a Stored Report, it can be printed from File — Print Stored Report, which opens the Print Stored Report window.
WARNING: What is stored in the database is a compressed binary image of the report output. This can be large and will increase the database size considerably if routine reports are repeatedly stored. While the database can handle this, it will increase the size of backups. Regular maintenance of Stored Reports using this window is recommended.
TIP: PostgreSQL Only Each stored report can take up allot of disc space on the server. You can see the scale of this in the File — System Manager — System Timing Test, then Print Results report. At the end of the report is a summary of TOAST tables (overflow tables). The REPFILE will show the extent of stored report excess disc space consumed.
When the window opens all stored reports are listed. Clicking on a list line will show the changeable data below including the selection of listed users and groups permitted to print the report in Print Stored Report.
You can edit the Subject and Comments of an individual stored report. The buttons below will become enabled if one or more report line is changed.
The selections in the Users and Groups lists can be changed to alter the saved report print privileges. You can multiple-select stored reports in the list and then select in the Users and Groups lists to apply the same privileges to all selected stored reports in one go.
To delete stored reports, multiple-select those you want removed from the database, and click the Delete Selected button.
|
Field |
Description |
|---|---|
|
Report List |
List of Stored Reports in the database. Multiple select for Delete or change access. |
|
Subject |
Reports stored output. Subject details. {REPFILE.REPSUBJ char 255} |
|
Comments |
Reports stored output. Comments. {REPFILE.REPCOMM char 100000000} |
|
User Access |
List of Users that can log on. Select those you want the stored report to be seen by. |
|
Group Access |
List of Groups. Select those you want the stored report to be seen by. |
|
Button |
Action |
|---|---|
|
Revert to Saved |
To revert any changes to the previously saved version. |
|
Save Changes |
To save the changes you have made to the data file. |
|
Delete Selected |
Click to delete the selected stored reports. |
|
Print Report |
Will cause a report to be printed of the subject matter. Right-click to change the report destination. You can not print to the Stored report destination. |
| See also: – |
Compiled in Program Version 5.10. Help data last modified 22 Sep 2017 10:44:28.65. Class wRepStoredMaint last modified 10 Oct 2017 11:48:39.
Reference Contents > Advanced Functions > Stored Report Maintenance
