The report is based on a temporary table.įor more information, see How to: Override the fetch Method to Filter Data for Reports (MorphX Reporting Tools). ![]() Some of the fetched data must be processed (this can also be done on the send method). The following are reasons for overriding the fetch method: The cycle continues with calls to next, get, and so on, until all the data has been fetched. The send, the header and/or footer methods, and the progressInfo method are then executed. The fetch method instantiates a query, opens the query prompt, and then fetches the records.ĭuring the execution of the fetch method, the next and get methods are executed in pairs on the query of the report. This method can be overridden to add fields to the Reports dialog box.įetches records from the database. You can override this method to use a different form.ĭoes nothing. This method opens the SysPrintProgress form. For reports that are only one page long, the progress indicator does not appear. This presents a progress indicator to the user, which is visible until all the data has been fetched and can be displayed. ![]() The following table describes the report methods that you can override.Ĭreates a caption when previewing a report, or a document name when printing a report.Ĭalled when the fetch method is being executed. They can be manipulated in overridden methods. These nodes have references to the member objects of the report. Methods That Can Be OverriddenĮach report in the AOT has child nodes named Data Sources and Designs. Methods written in a table are available to any report that uses that table as a data source. Whenever possible, write your code in the underlying table instead of in the report.
0 Comments
Leave a Reply. |