Workbench User Guide > Workbench User Guide > Managing and Deploying Applications > How You Can Apply Template Changes to Frames and Fields > Command Line Method for Upgrading Templates (ApplyTemplate)
Was this helpful?
Command Line Method for Upgrading Templates (ApplyTemplate)
To upgrade your frames and fields that have been previously generated, start the ApplyTemplate utility by entering the following command at the command line:
w4gldev runimage applytmp.img [-ccomponent] [-uusername] [-ddatabase]
    [-menvironment_var] [-gfilename] [-ifilename]
    [-nowindows] [-fakefields] [-bidi]
    [-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-Ttitletitle] [-A]
    [-Lfilename] [-/dbmsflags dbmsflags] [-/appflags appflags]
Note:  The following parameters and flags are available from the command line:
applytmp.img
Specifies the image file used to apply the template upgrade
-ccomponent
Specifies a component (frame or procedure) to use as the starting point for the application. By default, the application starts with the frame or procedure specified in the application's Property Inspector.
-uusername
Lets you use this command as if you were another user, username.
Note:  You, not username, own all files created by OpenROAD.
-ddatabase
Specifies the name and location (host machine) of the database that contains the data to be used in the application. This database need not be the same database that was specified when the application was created.
-menvironment_var
Lets you specify the name of a different environment variable to contain your list of DLLs or shared libraries to be searched when resolving 3GL procedure calls. If it is present, the -m parameter overrides any existing specification of II_LIBU3GL.
-gfilename
Specifies a file containing initial values for the global variables and global constants in the application.
The values remain in effect for the duration of the current OpenROAD session.
For more information about creating an initialization file, see Specify Initial Values for Global Variables and Global Constants.
-ifilename
Lets you specify a file containing overrides for the version and location of any included applications.
For more information about specifying an override file, see How You Can Image Included Applications.
-nowindows
Lets the application run without the window manager running. This option does not provide full batch mode execution, because some interaction with the application still may be required through the Trace window.
-fakefields
Instructs OpenROAD to multiplex a single control for many fields to save time and memory. By default, OpenROAD creates a separate Microsoft Windows system control for each field on a form.
This parameter is provided for backward compatibility. It sets the FormField.RequireRealField runtime default to FALSE.
Note:  Some field types only provide all their capabilities when they are created as Windows system controls.
-bidi
Specifies that OpenROAD application GUI components be displayed from right to left
-T
Controls the display of the Trace window by entering one of the following values:
yes
Specifies that the Trace window appears but suppresses all informational system messages
yes,min
Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed
yes,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages
all
Specifies that the Trace window does appear and all messages are written
all,min
Specifies that messages are written to the Trace window, which appears minimized as an icon
all,logonly
Specifies that the Trace window does not appear, but all messages are saved in a log file
no
Specifies that the Trace window does not appear, and no log file is created
-Ttitletitle
Replaces the title of the OpenROAD Trace window with title. If the title contains spaces, you must enclose it with single or double quotes.
-A
Appends the trace output of the current command to the end of the existing error log file.
Note:  The error log file, w4gl.log, is located in %II_SYSTEM%\ingres\files.
-Lfilename
Specifies the name of a log file. If the log path specified is not a full path, the file is created in the %II_SYSTEM%\ingres\files directory. You may include the following replacement parameters in the file name.
%p
Replaced by the Process Identifier (PID)
%d
Replaced by the current date in YYYYMMDD format
%t
Replaced by the current time in HH_MM_SS format
-/dbmsflags and -/appflags
An exit code of zero (0) means success; a non-zero exit code indicates an error.
Last modified date: 12/20/2023