Eloquence A.05.01 Release Notes

New features

Installation

In the subdirectory pa1.0 are programs which are using the PA-RISC 1.0 instruction set and are compatible with any HP9000 system.

In the subdirectory pa1.1 are programs which are using the PA-RISC 1.1 instruction set. These programs are not compatible with the following HP9000 systems: HP 9000/8x0, HP9000/8x5, HP9000/8x2

The install program will automatically install the appropriate program version.

eloqnd now included in runtime product

Starting with Eloquence release A.05.01 it will be included in both products.

Known problems fixed with A.05.01

MFORM.PROG

DISABLE

core dump after ERROR 8

DBINFO 202 failed on remote database

CRTCOLS caused core dump

refresh caused dialog to disappear

POPUP BOX

• The first line may not be visible.
• Default button of POPUP BOX does not have the focus.

dbstore/dbrestore

schema

ELOQDB.DLL

• DBFIND on index item does not work. This is a problem in the conversion of the lookup value. PA-RISC and PC systems have different character sets and have a different order of binary values. So each value must be converted before is is understood by the remote system.

• PC applications calling the ELOQDB.DLL aborted with a GPF if not compiled in large memory model. ELOQDB.H did not declare status as FAR. If not compiled with large memory model (where all pointers are far), a pc application became aborted with a GPF.

Known problems not fixed with A.05.01

• Debugging a program which causes error 12 may result a core dump.

  The following steps are required to reproduce:

     LOAD "CORE12"     --> ERROR 12
      
      
     STOP   
                --> ERROR 12
                --> core dump (bus error)
  
     10 ! RE-STORE "CORE12,LOCAL"
     20 OPTION BASE 1
     30 Bug: DISP "Start"
     40 ON KEY #1:"END" GOTO End
     50 WAIT
     60 Bug: DISP "Duplicate label"
     70 WAIT
     80 End:STOP
  

• REQUESTing a PORT outside the range of 11 to 20 causes an internal error

     assertion failed: (port >= 11 && port <= 20 && type == 0)
  

  if leaving Eloquence and the PORT has not been RELEASEd.

• A DBGET mode 15 or 16 after a DBFIND mode 4 or 5 does only validate the leading string part of the given regular expression, whereas the first DBGET should always evaluate the search expression.

  For example:

      DBFIND(Db$,"SET",4,S(*),"INDEX","AB[0-9]*")
      DBGET(Db$,"SET",15,S(*),Buf$,"@",0)
  

  The DBGET mode 15 retrieves all data that start with "AB".

  This is caused by the way, DBFIND and DBGET on index items is implemented. A DBFIND on an index saves the search expression for use by a subsequent DBGET and locates the first matching key. DBFIND mode 4 or 5 locates the first matching key, based on the leading string part of the regular expression. If no matching key is found, a status 17 is returned. A subsequent DBGET will start reading from the index using the saved search expression. However DBGET mode 15 and 16 will not check the result against the search expression.

  As a workaround, the first DBGET after a DBFIND mode 4 or 5 should always have mode 5 or 6.