Running Action Browser

You may run the Action Browser for an existing or a new application or resource database. Actions to be processed in the application must be defined in the resource database (functions) or must be available as external resources (command or batch files, programs).

You may run the Action Browser after installing ODABA . The Action Browser is platform independent and can be used on Windows, LINUX and several UNIX platforms. The Action Browser requires a project resource database (dictionary), but no specific resources defined in the dictionary.

Running the Action Browser usually requires separate specifications for data source and resource database. Theoretically, one could always use the ode.sys database as dictionary, since data types going to be processed are part of the system dictionary. When configuring an application database, this might affect the schema version in the database, which makes the database inaccessible when running with the application resource database, again.

Action Browser can be called from a command line in DOS or UNIX.

.../odaba/ode90.exe ini_file [ options ]

ode90.exe is the generic GUI framework, which is called as entry point for all ODABA applications. In order to call the proper application, the PROJECT option has to be set to ActionBrowser , which might be defined in the configuration or ini-file or as additional option passed on a command line.

The ini_file refers to the database location and can be provided as configuration or ini-file. Below you will find examples for an ini-file. In the DATA_DB section, application dictionary and database have to be defined.

In order to reduce the number of required ini-files and command files, one may use the ini-file as being provided with the installatin, which refers to a symbolic database path referenced by the DBPath option. Calling the Action Browser, any number of options can be passed preceded with a '-' sign:

ode90.exe cmd/ode.ini - PROJECT =ActionBrowser - DBPath =projects\sample\sample.dev - TRACE =log

Using options allows running different ODABA GUI applications with only one configuration or ini-file. Instead of passing option parameters, might also also set options in a command or bat file as in the example below. In contrast to options set in command or ini-files, which must never bequoted, options passed on the command line have to be quoted when containing spaces.

DBPath is a option, which has been defined in the ini-file for the DATABASE option in order to support dynamic path locations. Since DATABASE might be referenced in different sections of the ini-file, it is more save to refer to the more specific variable DBPath .

Details for configuring data source are described in in the WEB documentation under Data source definition .