Progress
Results User’s Guide
for UNIX
Using the Generated Report, Labels, and Data Export Code
This section describes how to use report, label, and data export programs generated by Results as stand-alone procedures.
In some situations, you might want to include some existing standard reports, label programs, and data export capabilities in your application without including all of the Results system. You can use Results to build these items yourself, then apply the following method to run them as standalone programs.
When you run a report, label, or data export definition, Results generates a Progress 4GL procedure. When you save these definitions in Results, you enter descriptions to identify them. (These are just descriptions, not the filenames used to store the reports as source files in the operating system.)
Build and test a sample/text report, label, etc. Once you have saved it, you can use the Contents of a User Directory option in the Administration module to look up the actual filename Results used to save your work.
For this example, assume you have generated a report program that Results saved in the operating system as rep00001.p. If you look at the rep00001.p file, you see that Results generated the Progress 4GL source code to run your report.
To run the 4GL source by itself, however, you first have to define the output destination. For example, you can define the output destination as lpr:
Many reports require you to use a PAGED output destination. For example, if the header within your source contains a field, use a PAGED output destination.
NOTE: Results cannot run any report, label, or data export program as a stand-alone procedure if it uses Ask mode in the WHERE clause builder.For all modules, the shared variable
qbf-total
returns the number of labels printed or records exported or reported.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |