Run an Application from the Database Using the RunDBApp Utility

To run an application from a database, start the RunDBApp utility in one of the following ways:

• (Windows only) Access RunDBApp through the Start menu, Run command

w4gldev rundbapp database application [-ccomponent]
    [-uusername] [-menvironment_var] [-gfilename] [-ifilename]
    [-nowindows] [-fakefields] [-bidi] [-vversion]
    [-T{yes|yes,min|yes,logonly|all|all,min|all,logonly|no}] [-A] [-Lfilename]
    [-/dbmsflags dbmsflags] [-/appflags appflags]

Specifies the name and location of the database in which the application resides

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.

Lets you use this command as if you were another user, username

Note: You, not username, own all files created by OpenROAD.

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, this parameter overrides any existing specification of II_LIBU3GL.

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.

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.

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.

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.

Displays OpenROAD application GUI components from right to left.

Controls the display of the Trace window by entering one of the following values:

Specifies that the Trace window appears but suppresses all informational system messages

Specifies that the Trace window appears minimized as an icon, and all informational system messages are suppressed

Specifies that the Trace window does not appear, but all messages are saved in a log file without informational system messages

Specifies that the Trace window does appear and all messages are written

Specifies that messages are written to the Trace window, which appears minimized as an icon

Specifies that the Trace window does not appear, but all messages are saved in a log file

Specifies that the Trace window does not appear, and no log file is created

Appends the trace output of the current command to the end of the existing error log file. Otherwise, that log file is replaced. This entry field can be used only if Execute in Background is enabled.

Note: The error log file, w4gl.log, is located in %USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID. If the -L flag is passed, a new name and location can be provided for the OpenROAD log file.

Note: 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.

An exit code of zero (0) means success; a non-zero exit code indicates an error. The exit code can be set by the application executed using the SessionObject.ExitCode attribute.