<<

Contents

Search

>>

 

GET_NEXT_RECORD

 

 

Function

 

 

Syntax:

GET_NEXT_RECORD(<Name of Index File>)

 

<Name of Index File> = <INDEXFILE>

 

Meaning:

Reads the next physical data record of an Ebus Index File.

 

GET_FIRST_RECORD and GET_NEXT_RECORD do not read the data records of an index file by a key, but in the order in which the records are physically stored in the data file.

 

Before GET_NEXT_RECORD is called the first time, GET_FIRST_RECORD must be called. The file pointer is then set to the beginning of the file. With GET_NEXT_RECORD the next stored data record is read.

 

The functions GET_FIRST_RECORD und GET_NEXT_RECORD be used in order to read all data records of an Index File with many data records faster than with START and READ-NEXT. GET_FIRST_RECORD and GET_NEXT_RECORD are up to four times as quick as START and READ-NEXT.

 

Note: ON INDEXERROR MACRO and ON READ(<INDEXDATEI>) MACRO are not executed with this function.

 

GET_NEXT_RECORD returns the following results:

 

Result

Meaning

 1

No error

-1

No further data record available

-2

<Name of Index File> is an JDBC Index File.

 

Parameter:

Name of Index File

Name of Index File

 

Sample:

H% = GET_FIRST_RECORD(CUSTOMER)

WHILE H% = 1

DO H% = GET_NEXT_RECORD(CUSTOMER)

...

ENDDO

 

See also:

GET_FIRST_RECORD

START

READ-NEXT