-
DBERASE / DBCREATE statement compatibility
When using eloqdb6, the optional maintenace word is no longer used.
You should use the DBLOGON statement to establish a user
with sufficient capabilities.
-
The dbtables utility does currently not report collating
sequences and data set capacity.
-
Cross reference (list -x) complains about user defined types
The cross reference (list -x) currently has some problems dealing
with user defined types (STRUCT). It is complaining about
multiply declared or unused member variables. (#458)
-
The TopItem attribute is currently not recognized by the
DLGSRV as a mapped attribute. As a workaround, you could use TopItem
as a native attribute. Just separate the attribute and
object path with an exclamation mark instead of a dot. (#450)
DLG SET "Dialog.ListBox!TopItem",3
-
The .h attribute is currently ignored by DLGSRV for PushButton
objects. As a workaround, you could use Height
as a native attribute. Just separate the attribute and
object path with an exclamation mark instead of a dot. (#463)
DLG SET "Dialog.Pb_OK!Height",3
-
HP Eloquence does not accept an implied LET using a
structured type after a THEN.
As a workaround, simply use explicit LET. (#392)
IF Condition THEN LET Instance.Member=25
-
The HP Eloquence syntax analyse results in a syntax error with
the statement below:
FOR I=1 TO A STEP C
The problem is, that the keyword AS is recognized errorneously.
As a workaround, simply use a different variable name or use an
expression (eg. A+0). (#454)
- QFIND with IN clause on an index may return
unexpected results if the collating sequence of the index and the
program executing QFIND is different.
QFIND internally uses DBFIND to position into the index and then
retrieves data in index order until the max. value is exhausted.
However the max. value is checked using collating sequence (this is
required to handle national characters properly, eg. in German A umlaut
needs to be inserted between A and B).
If the max. value is greater (or less) than the first index value
retrieved from the index, this will result in either an empty result
or an unexpected number of result records. (#493).