Language:

HansaManuals

Creating a Report Using the Report Generator
Creating a Report Generator Report - Specifying the Primary Register
Creating a Report Generator Report - The Appearance of the Report
   - Adding a Report Title
   - Adding Column Headings
   - Adding Fields to the Report
Creating a Report Generator Report - Choosing a Print Destination
Creating a Report Generator Report - The Width of the Report Window
Creating a Report Generator Report - Printing the Report
Creating a Report Generator Report - Adding White Space
Creating a Report Generator Report - Adding Searches
Creating a Report Generator Report - Adding a Secondary Register
Creating a Report Generator Report - Using Variables and Formulae
Creating a Report Generator Report - Printing Information from Matrices
Creating a Report Generator Report - Bringing Information in from Other Registers
Creating a Report Generator Report - Page Breaks
Creating a Report Generator Report - Filtering Records (Print If)
Creating a Report Generator Report - Adding Check Boxes to the Specification Window
Creating a Report Generator Report - Adding Radio Buttons to the Specification Window
Creating a Report Generator Report - Searching for Records within a Period
Creating a Report Generator Report - Break Points, Subtotals and Totals
Creating a Report Generator Report - Blocks
Creating a Report Generator Report - Syntax
Creating a Report Generator Report - Useful Functions
Example Reports - Listing Sales Figures
Creating a Report Generator Report - Common Error Messages

Tutorials for Standard Accounts

Creating a Report Generator Report - Adding a Search - Testing

As you build up the design of a Report Generator report, it's a good idea to test each step, so that you can catch errors early. With the Report Definition window open, you can do this in three ways:
  1. Click the [Check] button in the header of the Report Definition window. This will check that there are no syntax errors in the report, and will find some (though not all) logic errors as well. If there is an error, you will be told the nature of the error and the appropriate dialogue box will be opened so you can correct it. Please refer to the Common Errors page for details of some of the more common error messages.

  2. Click the [Run] button in the header of the Report Definition window to print the report. This allows you to check that the appearance of the report is correct. If there is a syntax error that would have been caught by the [Check] button, the report will not be printed.

  3. The [Check] and [Run] buttons will not find every logic error. You should therefore read through the report display areas on the 'Data' and 'Layout' cards extremely carefully to check the logic of your report before attempting to print it. Drawing up a Report Definition is effectively programming your copy of Standard ERP. As with programming of any kind, a bad logic error in a Report Definition may cause Standard ERP to crash.

!

Check the logic in your report extremely carefully. An error in report logic may cause Standard ERP to crash, with the risk of losing data.


It's also a good idea to save the Report Definition frequently as you proceed through the design process. However, the [Check] and [Run] buttons will include the latest unsaved changes, if there are any.

To test the Category search that we added here, click the [Run] button in the Report Definition window. The specification window appears, and now includes a Category variable:

Enter a Category by typing or by using the 'Paste Special' list that was attached to the variable in the 'Variable' dialogue box. Then click the [Run] button. In the illustration below, we searched for Customers belonging to the "CUST" Category. This information is shown in the report header on the right. The search is case-sensitive, so searching for "cust" would have resulted in an empty report.

Please follow the links below for more details about:
---

Creating a Report Generator Report:

Go back to: