Running Option Browser
One may run the OptionBrowser for an existing or a new application or resource database. Options to be set in a application database depend on the option schema provided in the application resource database.
OptionBrowser can be called from a command line in DOS or UNIX.
...ode.exeini_file [ options ] // windows
...codeini_file [ options ] // Linux
(c)ode 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 OptionBrowser, which might be defined in the configuration or ini-file or as additional option passed on a command line.
Running OptionBrowser usually requires separate specifications for data source and resource database. Theoretically, one could always use the ode.sys as dictionary, since data types going to be processed are part of the system dictionary. When configuring an application database, this may, however, change the schema version in the database which makes the database inaccessible when running with the application resource database.
# linux
LD_LIBRARY_PATH=/lib:/usr/lib/:%ODABA_ROOT%lib \
%PROGPATH%/code OptionBrowser.ini code
.. Windows
@echo off
:: ODE startup wrapper script
:: ODABA_ROOT should be the folder where you installed ODABA
set ODABA_ROOT=...odaba root path
cd /D "%ODABA_ROOT%"
start "" ode.exe OptionBrowser.ini
exit
Never run a database with different dictionary versions. Since opening a database, usually updates the schema version from the version of the current dictionary, this may cause schema version conflicts.
The resource database location and can be defined in as configuration or ini-file. The database referenced in the ini-file is required for storing current settings (options) and temporary data. Below there is an example for an ini-file. The DATADB section refers to the application database location.
[SYSTEM]
DICTIONARY=ode.sys
;[ode] under Windows
[code]
SYSDB=ode.sys
RESDB=ode.dev
DATDB=myProj.dat
SHARE=YES
PROJECT=OptionBrowser
PROJECT_DLL=Designer
In order to reduce the number of required ini-files and command files, one may use the ini-file as being provided with the installation, which refers to a symbolic database path referenced by the DATDB option. Calling the Option Browser, any number of options can be passed preceded with a '-' sign:
code OptionBrowser.ini -PROJECT=OptionBrowser -DATDB=projects\sample\myProj.dat
Using options allows running different ODABA GUI applications with only one configuration or ini-file. Instead of passing option parameters, one may also set environment variables in a command or bat file. In contrast to options set in command or ini-files, which must never be quoted, options passed on the command line have to be quoted when containing spaces.
DATDB is an option, which has been defined in the ini-file for the DATABASE option in order to support dynamic path locations.
Instead of passing parameter options, one may also define corresponding environment variables.
Details for configuring data source are described in in the WEB documentation under Reference documentation/Database references/Data source definition.