This article describes how to generate reports from a shortcut, batch file, or command prompt.
When you click the Generate button in FRx, the FRx Engine is started with parameters that specify the appropriate report options to be used for the report. When a report is created in FRx, the engine may be called to generate the report without using FRx Designer or Report Launcher. This is useful for generating reports from a desktop shortcut, a batch file, or a command prompt. The report will generate the same as it would within Designer or Report Launcher.
To generate a report that has the appropriate options, you must first understand the parameters that are used by the FRx engine. There are two kinds of parameters; those that require a value, and those do not. These parameters are explained here.
Parameters that require a value
|/I||FRx Catalog ID||Required|
|/C||FRx Company Code||Required|
|/B||Base Period||Not required – default base period is used if a value is not supplied|
|/Y||Year||Not required – default base period is used if a value is not supplied|
|/M||Database Password||Required only if GL or database security is needed to access the company|
|/U||FRx Username||Required only if FRx Security is enabled|
|/L||Database Login||Required only if GL or database security is needed to access the company|
|/FL||Forecaster Login||Required only if the report also includes FRx Forecaster data|
|/FP||Forecaster Password||Required only if the report also includes FRx Forecaster data|
Parameters that do not require a value
|/XRB||Rebuild the GL index (G32 file)||Not required|
|/XNL||Don’t process chained reports||Not required – chained reports will be generated if there are any and this is not supplied|
Note The /XRB and /XNL parameters must have a trailing colon. The examples shown here use this format.
Note Any command line that you create must begin with the path of the FRx engine (frxa32.exe). If FRx is installed in servershareFRx 6.7, you would have to begin your command line with “servershareFRx 6.7frxa32.exe”
Quotation Marks must be included around the path and file name, but not around the parameters.
Some sample command lines, together with explanations of what they do, are included here.
“servershareFRxfrxa32.exe” /I:BalSheet /C:FW /B:4 /Y:2002
“C:Program FilesFRx 6.7frxa32.exe” /I:INCSTMT /C:ABC /B:7 /Y:2009 /M:frx /U:bsmith /L:frx /XRB /XNL:
This command will generate the INCSTMT report for the ABC company for period 7 of 2009. The Engine will use bsmith for FRx security, and will log on to the GL database as the user “frx” with password “frx.” Catalogs chained to the INCSTMT catalog will not be processed.
“M:FRxfrxa32.exe” /I:Actual vs Budget /C:XYZ /M:frx /L:frx /FL:fc /FP:fcpw
This command will generate the “Actual vs Budget” report for the XYZ company and use the default base period that is saved in the catalog. The Engine will log on to the GL database as the user “frx” with password “frx” and will log on to the FRx Forecaster database as the user “fc” with password “fcpw.”
After you have assembled a command line for a report, you can use it to generate the report one time at a command prompt or in a batch file or shortcut that can be saved and double-clicked at any time to generate the report.
If your database username or password changes, you must make sure that you update it in the command line to prevent connectivity errors.
If you include logon and password information in a batch file or shortcut, make sure that you secure the file to prevent other users from accessing it.
Microsoft FRx Support will not help customers change, troubleshoot, or schedule batch files. This file is optional and is not required in order to use any Microsoft FRx application. FRx Software is not responsible for changes to the file that may cause files or systems to be deleted, damaged, or otherwise lost.