<Source>.ReadSeek (Function)

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Generic search/Exact-match search

Exact-match search in Access

Performing a search on a composite key

Search on an array item

Search and filter

Browsing the records corresponding to a condition

The views and RPC on HFSQL

Optimizing the browse operations

See also

<Source>.ReadSeek (Function)

In french: <Source>.LitRecherche

Not available with this kind of connection

Positions on the first file record whose value for a specific item is greater than or equal to a sought value (generic search). The record is read and the corresponding HFSQL variables are updated.

In most cases, <Source>.ReadSeek is used to set the position in the data file to perform a browse loop among the records that correspond to a condition. <Source>.ReadNext is used to read the next record corresponding to the condition.Several cases may occur after the call to <Source>.ReadSeek:

a record corresponding to the condition was found, locked (if necessary) and loaded in memory: <Source>.Found 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.
the data file is empty or there is no record corresponding to the condition: no reading is performed and <Source>.Out returns True.

This function can be used with the data files, HFSQL views or queries.

Remarks:

By default, <Source>.ReadSeekFirst and <Source>.ReadSeekLast are used to perform exact-match searches.
By default, <Source>.ReadSeek is used to perform a generic search on the character strings. This search is not a generic search on the integers, the reals, the dates, the currencies, ...

Versions 15 and later

This function is now available for Android applications.

New in version 15

This function is now available for Android applications.

Versions 17 and later

This function is now available for iPhone/iPad applications.

New in version 17

This function is now available for iPhone/iPad applications.

Versions 18 and later

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

New in version 18

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

Versions 21 and later

This function is now available in Universal Windows 10 App mode.

New in version 21

This function is now available in Universal Windows 10 App mode.

Example

// Find the first record
// for which the Customer name is MOORE
Customer.ReadSeek(Name, "MOORE")
IF Customer.Found() THEN
Trace("Customer MOORE found")
ELSE
Trace("Customer MOORE not found")
END

Syntax

<Result> = <Source>.ReadSeek(<Item> , <Sought value> [, <Options>])

<Result>: Boolean (optional)

Corresponds to:
True if the sought record was found and read. The file buffer is loaded with the data of the record found. In this case, HError is set to 0 and <Source>.Found is set to True.
False in the following cases:
error while accessing the file (unable to read for example). HError returns an error code. HErrorInfo returns more details about the error. In this case, <Source>.Found cannot be used.
the access to the file was performed but no record was found. In this case, HError is set to 0 and <Source>.Found is set to False.
Caution: In this case, the file buffer cannot be used.

<Source>: Type corresponding to the specified source

Name of data file, HFSQL view or query used.

<Item>: Character string (with or without quotes)

Name of item on which the search will be performed.
For an exact-match search, this parameter can correspond to a non-key item.
To perform generic searches on a composite key, all the components of the composite key must be text components. Otherwise, an exact-match search is performed.

<Sought value>: Type corresponding to the value

Value of sought item.

<Options>: Optional constant (or combination of constants)

Used to configure:
the lock mode applied to the sought record.
the type of search performed.
hLockWrite Lock in write mode: the record currently read can be read by another application but it cannot be modified by another application.
The lock mode is ignored if a query is used.
The management of locks is not available.
Access by JDBC: This constant is not available.
hLockReadWrite Lock in read/write: the record currently read cannot be read or modified by another application.
The lock mode is ignored if a query is used.
Lock in write-only. Operating mode equivalent to the hLockWrite constant.
The management of locks is not available.
Access by JDBC: This constant is not available.
hLockNo No lock (even if HStartLock was called): the record can be read or modified by another application during the reading.
The management of locks is not available.
Access by JDBC: This constant is not available.
hIdentical Exact-match search (see the Notes)
A generic search is performed by default (constant not specified).
Access by JDBC: This constant is not available.
hLimitParsing
The browse will stop as soon as the last sought value is found. The current record will correspond to this last record found.
<Source>.Found will be set to False and <Source>.Out will be set to True.
This constant is used to optimize the search speed in Client/Server mode.
This constant is recommended when performing a simple search (without browsing the elements found).
This constant is not available.
hKeepFilter The filter implemented by <Source>.Filter will be taken into account, even if the search key is not optimized for the filter. Reminder: <Source>.Filter returns the search key optimized for the filter.
Caution: in this case, performance issues may arise for large files.
This variable cannot be used.
hNoRefresh
<Source>.ReadSeek does not refresh the content of the table or query. If possible, the query is not re-run. All the saved positions are stored.
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.
The lock options will have no effect if the locks are not supported by the OLE DB provider or by the Native Connector.
Access by JDBC: The management of locks is not available for databases accessed by JDBC.

Remarks

Generic search/Exact-match search

A generic search or an exact-match search will be performed according to <Sought value>.

Generic search: search for all the records that start with the specified value
To perform a generic search, the requested value must be specified in <Sought value>.
Remark: For backward compatibility with WINDEV 5.5, the generic search of an empty string ("") is equivalent to the use of <Source>.ReadFirst.
Exact-match search: search for all the records that exactly correspond to the specified value.
To perform an exact-match search, the size of the search argument must be exactly the same as the size of the key. To perform an exact-match search, you also have the ability to use the hIdentical constant.
To perform an exact-match search, you also have the ability to use <Source>.ReadSeekFirst.

Caution: If you are using Hyper File 5.5 files or files in Hyper File 5.5 format migrated to HFSQL Classic, the implementation of generic searches and exact-match searches may change. See the Hyper File 5.5 and HFSQL Classic: How to manage the space characters in the searches? table for more details

Exact-match search in Access

To perform an exact-match search on an ACCESS database, it is recommended to use NoSpace if there are space characters at the end of the sought value.

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,
Using <Source>.BuildKeyValue,
Using HConvert.

1. Using a list of values

The following syntax is used to perform a search on a composite key:

HReadSeek(<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
Customer.ReadSeek(LastName_FirstName, ["MOORE","Vince"])

WHILE Customer.Found()
// Process
Customer.ReadNext(LastName_FirstName)
END

2. Using <Source>.BuildKeyValue

If the sought item is a composite key, the value to find can be built by <Source>.BuildKeyValue.

3. Using HConvert (backward compatibility with WINDEV 5.5)

To build the value of a composite key without using <Source>.BuildKeyValue, you must:

fill the text components on their entire size with Charact(0).
convert the numeric components with HConvert.

Example:

MyCompositeKey = Complete(Customer.CustomerLastName, Dimension(Customer.LastName), Charact(0)) + ...
Complete(Customer.FirstName, Dimension(Customer.FirstName), Charact(0))

To perform generic searches on a composite key, all the components of the 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 whose subscript is 1). To perform a search on the other array elements, use the filters or queries.

Search and filter

If a filter is enabled (<Source>.Filter), the filter is taken into account by the search only if the key used is identical.

Browsing the records corresponding to a condition

In most cases, <Source>.ReadSeek is used to set the position in the data file to perform a browse loop among the records that correspond to a condition. <Source>.ReadNext and <Source>.ReadPrevious are used to read the next and previous records corresponding to the condition.

To ignore the search while going to the next or previous record, use one of the following functions:

The views and RPC on HFSQL

The search on a HFSQL view via a remote access (RPC on HFSQL) operates according to two different methods:

if the group of records selected by the view has not been previously brought back to the local computer, a call to the server is performed in order to search for the specified value.
This solution is recommended if the size of the view is important and/or if a small number of searches must be performed.
if the group of records selected by the view has been previously brought back to the local computer, the search is performed on the local computer directly (no need to call the server).
This solution is recommended if the size of the view is not very important and/or if a large number of searches must be performed.
To bring back all the records selected by the view to the local computer, you can:
- call <Source>.CreateView and specify a significant number of records per page (<Page size> parameter) then start the search with <Source>.ReadFirst (recommended method).
- create a loop used to browse all the records selected by the view (<Source>.ReadFirst and <Source>.ReadNext).
  Remark: This solution triggers an important exchange of data during the first access to the view.

Optimizing the browse operations

To improve the first browse times on a data file, use <Source>.Optimize on this data file.

Component : wd250hf.dll