contact contact

Eloquence known problems and fixes
All platforms

  This page documents known problems with Eloquence which are either not related to code defects or have a low priority because an easy workaround is available.

Please note: This page is provided in the intention to be helpful to our customers. However the information is provided "AS IS" without any warranty.

All platforms

  • A scanner anomaly has been detected. The statement "NEW Fu_ns AS New_sales" results in a syntax error due to a conflict with the ASN keyword. As a workaround you should use a colon instead of AS: "NEW Fu_ns:New_sales" which is equivalent (#663).

  • A FIND statement could result in a ERR 247. On stderr the following message is output:
    db status [1944] = 11 318 0 7224 0 405 0 0 2 0
    An ERR 247 means that an unexpected database status was encountered during the FIND operation. This message indicates a DBGET which failed with status 11. This is probably related to an optimization attempt of a subsequent FIND statement which ignores datasets with no active IN DATA SET .. USE since this would have no influence on the result.
    When FIND is executed with no active variable link it could fail with a runtime error 247. This problem is also present in previous releases. (#587)

    When using B.06.32 with eloqdb6 this should no longer happen.

  • Handling programs with embedded NUL characters (#606)

    The HP260 made it possible to embed NUL characters into strings. While Eloquence is able to execute such a program, the program listing is inconsistent, since a NUL character is used internally as a string terminator. This may cause program corruption if such a program line is modified. Embedded NUL characters are now converted into a CHR$(0) expression. However this may cause a syntax error when a string constant is replaced by an expression due to an embedded NUL character when only a string constant is valid.

  • The dbtables utility does currently not report collating sequences.

  • Eloquence does not accept an implied LET using a structured type after a THEN. As a workaround, use an explicit LET. (#392)
    IF Condition THEN LET Instance.Member=25

  • The Eloquence syntax analyse results in a syntax error with the statement below:
    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).

  Privacy | Webmaster | Terms of use | Impressum Revision:  1998-05-26  
  Copyright © 1995-2002 Marxmeier Software AG