Progress
Report Builder
User’s Guide
Report Builder Startup Parameters
Table A–2 lists the Report Builder startup parameters and their syntax.
Table A–2: Report Builder Startup Parameters Parameter Syntax Report Code Page In1 Report Code Page Out UDF Code Page In1 UDF Code Page Out Explicit Join1
The remainder of this section describes each startup parameter in alphabetical order by operating system syntax. See the "Internationalization" section for more information about using these parameters.
Report Code Page In (-rbcpreportin)
codepage
Name of code page to use for the report.
This parameter allows you to override the code page name stored in any reports you open. When you save a report, Report Builder assigns it a code page. When Report Builder and Report Engine attempt to read the report, the -rbcpreportin parameter tells them to treat the report as being in the specified code page. If you do not specify a value, Report Builder and Report Engine use whatever code page was assigned to the report when it was last saved.
For example, set the Report Code Page In parameter to UNDEFINED if you are developing reports that will be run in many different environments with different code pages and you do not use constant character strings in the report.
Report Code Page Out (-rbcpreportout)
codepage
Name of code page to use for the report when it is saved.
This parameter allows you to override the default code page Report Builder uses when storing a report. When you save a report, Report Builder assigns it a code page. When Report Builder attempts to save the report, the -rbcpreportout parameter tells Report Builder to save the report using the specified code page. If you do not specify a value, Report Builder saves the report in the code page specified by the -cpinternal parameter.
This parameter has no effect on any other reports in the report library — it affects only the ones you explicitly save while running Report Builder with this parameter (for example. by using the Report
Save).
For example, set -rbcpreportin and -rbcreportout to “undefined” if you are developing reports that will run in many different environments with different code pages and you do not use constant character strings in the report:
If -rbcpreportin and -rbcreportout are both set to “undefined,” Report Builder does not attempt to convert between code pages when reading and writing reports. This enables you to create a report in one language, for example English, and later run it in another language configuration, for example Russian, without encountering errors because the code pages are incompatible.
UDF Code Page In (-rbcpudfin)
codepage
Name of code page to use for the user-defined function file.
This parameter allows you to override the code page name stored in the user-defined function file (
PRORB.UDF
). When you define a UDF, Report Builder assigns it a code page. When Report Builder and Report Engine attempt to read a report that uses a UDF, the -rbcpudfin parameter tells them to treat the UDF as being in the specified code page. If you do not specify a value, Report Builder and Report Engine use whatever code page was assigned to the UDF when it was last saved.UDF Code Page Out (-rbcpudfout)
codepage
Name of code page to use for the user-defined function file when it is saved.
This parameter allows you to override the default code page Report Builder uses when storing a user-defined function. When you create or modify a UDF, Report Builder assigns it a code page. When Report Builder attempts to save the UDF, the -rbcpudfout parameter tells Report Builder to save the UDF using the specified code page. If you do not specify a value, Report Builder uses whatever code page was assigned to the UDF when it was last saved. If this is the first time Report Builder is saving the UDF, it saves the UDF in the -cpinternal code page.
This parameter has no effect on other UDF’s that might already be in the UDF file — it applies only to the UDF’s that you edit or create while running Report Builder with this parameter.
Explicit Join (-rbexpjoins)
This parameter allows you to use explicit inner join syntax rather than the default implicit syntax. When explicit syntax is used, the behavior of the optimizer in the SQL Engine is altered. There are cases when this can be beneficial depending upon the amount of data, size of records, and the structure of the SQL query.
For example, there are queries where the optimizer will reorder the tables in the From clause of the Select statement. This causes the SQL Engine to process a larger table first, making the query run slower. In certain cases, using -rbexpjoins helps reports run faster.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |