Progress
Results Administration
and Development Guide
Converted Information
This section describes the information that the Converter converts from character-based to graphical format. The Converter converts the following information:
NOTE: Before converting your files, note that the graphical Results procedure library (aderes.pl
) and the Converter r-code ($DLC/gui)
must be in yourPROPATH
.File Conversions
When the Converter converts Progress Version 6 or Version 7 character-based files, it converts them to the closest Progress Version 9 graphical equivalent.
Table 5–1 lists the original character-based files and their graphical equivalents.
Printer Information
For each printer definition, the Converter creates a feature and adds it to the Results Query
Print menu. The printer type dictates how the information is converted. Table 5–2 lists the printer conversion information.
Auto Selection of Label Fields
The label field information in the configuration file converts without any changes.
Module and Query Function Permissions
Module permission provides site security for each module. Query function permissions provide security for each type of query. The Converter converts both types of permissions and adds the information to the security portion of the graphical configuration file. When there is no corresponding graphical feature for a character-based feature, the Converter does not convert the character-based feature. Table 5–3 lists the query feature conversions.
Report Layout
The report layout portion of the configuration file sets the default layout for a report. The converter converts all of this information, except for the header and footer information.
Relationships
The relationships portion of the configuration file identifies the relationships or joins for an application. All of this information converts to the graphical version of the configuration file.
View Files
The graphical and character-based versions of Results use the same basic techniques for saving query information. Both versions include a comment holding the query information at the beginning of a form, label, or export file. Both versions read this section to lay out the view in the user interface.
However, while both version have these similarities, the following differences exist between the two versions:
- Character-based query files include character-based 4GL. The Converter does not convert this code, but instead uses this information to create an equivalent query in the graphical 4GL.
- Graphical queries are defined only once. Each view type creates the user interface for the query. In contrast, if users want three views of a query in the character-based version, they must define each view separately. This technique creates three separate files. The converter does not attempt to decipher each of these files to check if they are for the same query; it simply converts each file into its graphical equivalent. The Results administrator must eliminate “duplicate” files.
Queries
The converter uses the character-based query directory file as an index to find all the user queries when it converts them.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |