Sets the position on the next data file record according to a browse item.
The record is not read.The number of the current record is modified when it is returned by
<Source>.RecNum. For the functions that handle the current record number (
<Source>.Delete,
<Source>.Read,
<Source>.Modify, ...), the value of this number is not updated: you must use
<Source>.RecNum(). For example: not to do:
but
Customer.Delete(Customer.RecNum())
The reading is performed from the lowest to the greatest value of the browse item (see the remarks for more details).
Caution: The record loaded in memory is not modified. The HFSQL variables (Customer.Name for example, which means the Name item of Customer file) are not updated.
In most cases,
<Source>.Next sets the position in the data file to browse through the records that correspond to a condition.
<Source>.Next is used to position on the next record corresponding to the condition.
Several cases may occur after the call to <Source>.Next:
- a record corresponding to the condition was found: <Source>.Found returns True
- the data file is empty or there is no record corresponding to the condition: <Source>.Out returns True
Remarks:
Versions 15 and later
New in version 15
Versions 17 and later
New in version 17
Versions 18 and later
New in version 18 Remark: From version 19, HFSQL is the new name of HyperFileSQL.
Versions 21 and later
New in version 21The read operation is performed from the lowest to the greatest value of the browse item (see remarks for more details).
Caution: The record loaded in memory is not modified. The HFSQL variables (Customer.Name for example, which means the Name item of Customer file) are not updated.
In most cases, <Source>.Next is used to position in the data file during a browse loop.
Several cases may occur after the call to <Source>.Next:
- the data file is empty or no record corresponds to the filter (defined by <Source>.Filter): <Source>.Out returns True
- the function tries to lock a record that is already locked in read-only: HErrorLock returns True and <Source>.Out returns True.
Locks are only managed on HFSQL Client/Server data files or data files handled by a Native Access. An HFSQL Mobile record cannot be locked. Indeed, the operating system of Pocket PC does not allow you to lock records.
Access by JDBC: The management of locks is not available for databases accessed by JDBC.
Versions 15 and later
New in version 15
Versions 17 and later
New in version 17
Versions 18 and later
New in version 18 Remark: From version 19, HFSQL is the new name of HyperFileSQL.
Versions 21 and later
New in version 21