ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Help / WLanguage / Managing databases / HFSQL / HFSQL functions
  • Generic search/Exact-match search
  • Performing a search on a composite key
  • Search on an array item
  • Search and filter
  • Locks
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Positions on the first file record whose value for a specific item is greater than or equal to a sought value. The record is not read.
The number of the current record is modified only when it is returned by HRecNum. For the functions that handle the current record number (HDelete, HRead, HModify, etc.), the value of this number is not updated: you must use HRecNum.
Example not to do:
// Deletes a record not corresponding to the expected one
HSeekFirst(Customer, CustomerID, 25)
HDelete(Customer)
but:
// Delete the sought record
HSeekFirst(Customer, CustomerID, 25)
HDelete(Customer, HRecNum())

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, HSeekFirst sets the position in the data file to loop through the records that match a condition.
Several cases may occur after the call to HSeekFirst:
  • a record corresponding to the condition was found, locked (if necessary) and loaded in memory: HFound returns True.
  • the data file is empty or there is no record corresponding to the condition: 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: the search can be canceled by HCancelSeek.
Example
// Find the first record for which
// the Customer name is Moore
HSeekFirst(Customer, Name, "Moore")
// The record is not read.
// Finds all the customers with a specific last and first names.
// The search is performed according to a composite key.
bufSoughtVal is Buffer = HBuildKeyValue(Customer, LastName_FirstName, sLastName, sFirstName)
HSeekFirst(Customer, LastName_FirstName, bufSoughtVal, hLockWrite)
WHILE HFound(Customer) = True
HDelete(Customer, HRecNum())
HNext(Customer, LastName_FirstName, hLockWrite)
END
Syntax
<Result> = HSeekFirst(<Data file> , <Key item> , <Sought value> [, <Options>])
<Result>: Boolean
  • True if the position was set on the record (corresponds to the value of HFound).
  • False if a problem occurs. This problem can be caused by:
    • a positioning problem (empty data file, etc.): HFound returns False and HError returns 0.
    • an error: HError returns an integer other than 0. HErrorInfo returns more details.
<Data file>: Character string
Name of the HFSQL data file used.
<Key item>: Character string
Name of key item on which the search will be performed.
<Sought value>: Type corresponding to the value
Value of the sought item.
<Options>: Optional constant (or combination of constants)
Configures:
  • the lock mode applied to the sought record
  • the type of search performed.
hGenericGeneric search (see the Notes)
An exact-match search is performed by default (constant not specified).
hKeepFilterThe filter set 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 problems may occur on large files.
Hyper File 5.5 This variable cannot be used.
By default, the iteration performed after HSeekFirst ignores the filter.
hLimitParsingThe iteration will stop when the last searched value is found. The current record will correspond to this last record found.
HFound will return False and HOut will return True.
This constant is used to optimize the search speed in Client/Server mode.
hLockNoNo lock: the record can be read or modified by another application during the reading.
hLockReadWriteLock in read/write: the record currently read cannot be read or modified by another application.
OLE DB Lock in write-only. Operating mode equivalent to the hLockWrite constant.
hLockWriteLock in write mode: the record currently read can be read by another application but it cannot be modified by another application.
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.
OLE DB The lock mode specified by HSeekFirst will remain effective during the calls to HPrevious and HNext.
To change the lock mode, use:
Remarks

Generic search/Exact-match search

  • Generic search (mainly on the Character String items): Finds all the records starting with the specified value.
    For example: When a generic search is performed on "Smith" (for the NAME item), all records whose Name item starts with "Smith" will match the search. Therefore, the record containing "Smither" will correspond to the search (HFound returns True).
  • Exact-match search: Finds all the records that exactly correspond to the specified value.
    For example: When an exact-match search is performed on "Smith" (for the NAME item), HFound returns True for the records whose item exactly matches "Smith".
  • Examples of searches performed on CUSTOMER file sorted by name:
Sought valueOptionsHSeekFirst sets the position on the recordHFound returnsHOut returnsExplanations
Durand1TrueFalseDurand exists.
The end of data file was not reached yet.
Dupuis1FalseFalseDupuis does not exist. Positioning on the first greater value (Durand).
The end of data file was not reached yet.
MoorhGeneric8TrueFalseMoor does not exist but the search is a generic search and Moore is found (among others).
The end of data file was not reached yet.
MoorThe record was not found (no move)FalseFalseMoor does not exist.
The end of data file was not reached yet.
NorbertThe record was not found (no move)FalseTrueNorbert does not exist.
Position on the first greater value (this value does not exist): The end of data file has been reached.
WEBDEV - Server codeAjaxHFSQL ClassicHFSQL Client/ServerHyper File 5.5OLE DBNative Connectors (Native Accesses)

Performing a search on a composite key

Several methods can be used to perform a search on a composite key:
Using a list of values
The following syntax is used to perform a search on a composite key:
HSeekFirst(<File name>, <Name of composite key>, ...
[<Search value of first element of composite key>,
<Search value of first element of composite key>, ...])

Example:
// Find the record
HSeekFirst(Customer, LastName_FirstName, ["Moore","Vince"])
Hyper File 5.5 To perform generic searches on a composite key, all the components of composite key must be Text components. Otherwise, an exact-match search is performed.

Search on an array item

The search is performed on the first array element (element with index 1). To perform a search on the other array elements, use the filters or queries.

Search and filter

If a filter is enabled (HFilter), the search takes the filter into account.
Hyper File 5.5 If a filter is enabled, the filter is ignored by the search.
WEBDEV - Server codeAjaxHFSQL ClassicHFSQL Client/ServerHyper File 5.5OLE DBNative Connectors (Native Accesses)

Locks

The locks apply only when a record was found.
By default (no lock mode specified in <Options>), the record is not locked.
If a lock is requested (hLockWrite or hLockReadWrite constant), the record will be read only if this record is not already locked.
Reminder: A locked record can be unlocked by HUnlockRecNum.
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.
Component: wd290hf.dll
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 07/15/2022

Send a report | Local help