Sets the position on the last record of a data file according to a browse item.
The record is not read.
The number of the current record is modified when it is returned by
HRecNum. For the functions that handle the current record number (
HDelete,
HRead,
HModify, ...), the value of this number is not updated: you must use
HRecNum(). For example: not to do:
but
HDelete(Customer, HRecNum())
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,
HLast sets the position in the data file to browse through the records that correspond to a condition.
HNext is used to position on the next record corresponding to the condition.
Several cases may occur after the call to HLast:
- a record corresponding to the condition was found: HFound returns True
- the data file is empty or there is no record corresponding to the condition: HOut returns True
Remarks:
- By default, HSeekFirst and HSeekLast are used to perform an exact-match search.
- By default, HLast is used to perform a generic search.
Versions 15 and later
New in version 15Versions 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 The read operation is performed for the greatest value of the browse item (see
remarks for more details).
Caution: The record loaded in memory is not modified. HFSQL variables (e. g. Customer.Name, or the Name item of the Customer data file) are not updated.
In most cases,
HLast is used to set the position in the data file in order to perform a read loop with
HPrevious.
Several cases may occur after the call to HLast:
- the data file is empty or no record corresponds to the filter (defined by HFilter): HOut returns True.
- the function tries to lock a record that is already locked in read-only: HErrorLock returns True and HOut returns True.
Locks are managed only on HFSQL Client/Server data files or on data files handled by a Native Connector. 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.
Management of locks not available in SQLite databases.
Versions 15 and later New in version 15 Versions 17 and later New in version 17 Versions 18 and later New in version 18 Versions 21 and later New in version 21 Remark: From version 19, HFSQL is the new name of HyperFileSQL.
// Browse a data file from the last record
HLast(Customer, Name)
WHILE NOT HOut()
// Process the record
HPrevious(Customer, Name)
END
Syntax
<Result> = HLast([<Data file>] [, <Search key item> [, <Options>]])
<Result>: Boolean
- True if the position was set,
- False if an error occurred. This problem can be caused by:
- a positioning problem (empty data file, ...): HFound returns False and HError returns 0.
- an error: HError returns an integer other than 0. HErrorInfo returns more details.
<Data file>: Optional character string (with or without quotes)
Name of data file used. If this parameter corresponds to an empty string (""), HLast will use the last data file used by the last HFSQL management function (function starting with "H").
<Search key item>: Optional character string (with or without quotes)
Name of key item used to browse the data file. If this name is not specified, HLast will use the last browse item used on this data file by the last HFSQL management function (function starting with "H"). If this item does not exist, the best browse item is automatically used.
<Options>: Optional constant
Configures the lock set on the record selected by HLast: | |
| hLockWrite | Lock in write mode: the selected record can be read by another application but it cannot be modified by another application.
|
| hKeepFilter | The filter implemented by HFilter will be taken into account, even if the search key is not optimized for the filter. Reminder: HFilter returns the search key optimized for the filter.
Caution: in this case, performance issues may arise for large files.
|
| hLockReadWrite | Lock in read/write: the selected record cannot be read or modified by another application. |
| hLockNo | No lock (even if HStartLock was called): the record can be read or modified by another application. |
| hNoRefresh | |
Remarks
Read operation according to a key
HLast sets the position on the record with the greatest key value.
The sort order is the one that was specified in the analysis for this key.
If duplicates are found, HLast sets the position on the first "duplicate" record according to the sequence of record numbers.
Various
- The current record number is returned by HRecNum.
- HChangeKey is used to modify the search key while remaining positioned on the current record.
Comparing HReadLast and HLast
HLast does not read the record: therefore,
HLast is faster than
HReadLast.