This content comes from an automatic translation.
  • Read operation according to a key
  • Checking the password
  • Various
  • Comparing HReadLast and HLast
  • Locks
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
Positions on the last file record according to a search item. The record is not read.
The number of the current record is only changed when it is returned by the HRecNum function. For functions that manipulate by default the number of the current record (functions HDelete, HRead, HModify,...), the value of this number is not updated: you must use HRecNum(). For example: not to do:
HDelete(Customer, HRecNum())

The reading is performed for the greatest value of search 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 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 there is no record corresponding 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.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.
// Browse a data file from the last record
HLast(Customer, Name)
// Process the record
HPrevious(Customer, Name)
<Result> = HLast([<Data file>] [, <Search key item> [, <Options>]])
<Result>: Boolean
  • True if the positioning was performed,
  • 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 (""), the HLast function manipulates the last data file used by the last HFSQL management function (function starting with the letter 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 handles the last search item used on this data file by the last function for HFSQL management (starting with the letter H). If this item does not exist, the best browse item is automatically used.
<Options>: Optional constant
Configures the lock performed on the record selected by HLast:
hLockWriteLock in write mode: the selected record can be read by another application but it cannot be modified by another application.
hKeepFilterThe 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, poor performance may occur on huge data files.
Hyper File 5.5 This constant cannot be used.
hLockReadWriteLock in read/write: the selected record cannot be read or modified by another application.
hLockNoNo lock (even if HStartLock was called): the record can be read or modified by another application.
OLE DBNative Connectors (Native Accesses) The table or query content will not be refreshed. All the saved positions are stored.
If this parameter is not specified, HLast reinitializes the browse for the specified item: the content of table or query is refreshed with the data found in the OLE DB database. All the saved positions are lost. The position will be restored according to the value of best item.
Remark: The browses and the positions saved on the other items are not affected.

OLE DBNative Connectors (Native Accesses) The lock options will have no effect if the locks are not supported by the OLE DB provider or by the Native Connector.
Hyper File 5.5 The lock options are ignored. Use the lock functions (HLockRecNum) kept for backward compatibility.

Read operation according to a key

HLast positions 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 positions on the last "duplicate" record according to the sequence of record numbers.
Reports and QueriesHFSQLHFSQL Client/ServerHyper File 5.5

Checking the password

If the HLast function is the first function to handle the specified data file, the password check is performed when the data file is opened.
If the password is incorrect, HErrorPassword returns True and HOut returns True.


  • The current record number is returned by HRecNum.
  • The HChangeKey function allows you to modify the route key, while remaining positioned on the current record.

Comparing HReadLast and HLast

The function HLast does not read the record: therefore, HLast is faster than HReadLast.
Reports and QueriesHFSQLHFSQL Client/ServerHyper File 5.5OLE DBNative Connectors (Native Accesses)


By default (parameter <Options> not specified), no blocking of the recording is performed.
If a lock is requested (hLockWrite or hLockReadWrite constant), the positioning on the record will be performed only if this record is not already locked.
There is no need to specify a lock parameter if the data file is locked by HStartLock: the lock specified by HStartLock is automatically taken into account. To ignore the lock specified with function HStartLock, use the constant hBlockNot.
Component : wd250hf.dll
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment