Datasheet
Release Notes - New Features included in Release 2.4.0
Page 58 of 89
4.3.1.3 TROPOS Form dynamic database access (SR4142)
TROPOS Form may now access an Oracle database via direct database accesses. Tables or views
may be accessed.
Manual Set-Up Procedures
None is mandatory – see below for technical description:
Single row, single column selects
The dbacn= clause in the LOGIC section of a wppform.out file may now contain a standard SQL
statement instead of a script name. The use of script names is still supported.
e.g.
dbac2=select custname from mbg110 where customer = :customer and account15_cus =
:account15;
Alternatively, the SQL statement may be wrapped over several lines by using a ‘\’ continuation
character as the last character on a line.
e.g.
LOGIC
dbac2=select custname \
from mbg110 \
where customer = :customer \
and account15_cus = :account15;
The statement must end in a ‘;’.
In the header section (in this case) or in the detail section (if suitably ‘link’ed to a triggering event),
the database access could be referenced as before:
e.g.
HEADER
f.custname=4,10 dbac=2
If a bind variable name (a data source in a ‘where’ clause – ‘customer’ and ‘account15’ above)
contains a ‘-’ (dash), then the syntax in the dbacn clause must contain ‘$_’ instead of ‘-’. (This is
because Oracle will reject dashes in variable names.)
e.g.
PARTNO-SORD T5540
...
dbac3=select DESCRIPTION from mbb010 where PARTNO = :partno$_sord ... etc
Alternatively, the ‘dbac=2’ clause could be put into the LOGIC section and linked to a dataname or
event in the same way as in the following multiple column example.
One difference between the two positions of the database access clause is that if a condition is
involved, a condition in the LOGIC section determines whether the database access is done at all,