<Source>.ReadSeekFirst (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

This content has been translated automatically. Click here to view the French version.

Help / WLanguage / Managing databases / HFSQL / HFSQL functions

Generic search/Exact-match search
Search performed on a key item or on a non-key item
Performing a search on a composite key
Search on an array item
Search and filter
Looping through records that match a condition
Exact-match search in Access
Locks
Optimizing iterations
Native XML Connector

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

<Source>.ReadSeekFirst (Function)

In french: <Source>.LitRecherchePremier

Not available with this kind of connection

Positions on the first record of a data file whose value for a specific item is strictly equal to a sought value (exact-match search). The record is read and the corresponding HFSQL variables are updated.

In most cases, <Source>.ReadSeekFirst sets the position in the data file to loop through the records that match a condition. <Source>.ReadNext is used to read the next record corresponding to the condition.

Several cases may occur after the call to <Source>.ReadSeekFirst:

a Record corresponding to the condition has been foundblocked (if necessary) and loaded into memory: function <Source>.Found returns True.
if there is no record corresponding to the condition, but if a record with a higher value exists the record is read, function <Source>.Out returns False and function <Source>.Found returns False.
the data file is empty no reading is performed, function <Source>.Out returns True and function <Source>.Found returns False.
the function attempts to block a record already blocked for playback: no playback is performed, function HErrorLock returns True and function <Source>.Out returns True.
Note: By default, a automatic management of lock errors and modification conflicts is performed (except in stored procedure code).. This assisted management of errors can be customized or disabled at any time by <Source>.OnError.

<Source>.ReadSeekFirst can be used with the data files, HFSQL views or queries.

Note: the search can be cancelled by pressing <Source>.CancelSeek..

Special case Blockage management:

In PHP, the management of locks is not available.
In Java, during an access through JDBC, the management of locks is not available for the databases accessed by JDBC.

Example

// Recherche du premier enregistrement pour lequel 
// le nom du Client est DUPOND
Client.LitRecherchePremier(Nom, "DUPOND")
IF Client.Trouve() = False THEN
	Error("Client non trouvé")
	RETURN
ELSE
	// Suite du traitement sur le client DUPOND
END

Syntax

<Result> = <Source>.ReadSeekFirst(<Item> , <Search value> [, <Options>])

<Result>: Boolean

True if the record was found (corresponds to the value returned by <Source>.Found).
False if a problem occurs. This problem can be caused by:
or a positioning problem (empty data file, etc.): function <Source>.Found returns False and function HError returns 0.
an error: HError returns an integer other than 0. HErrorInfo returns more details.

<Source>: Type corresponding to the specified source

Name of the HFSQL data file, view or query used.

<Item>: Character string

Name of item on which the search will be performed. This item can be a search key or not.
The search can only be performed on a key item.

<Search value>: Type corresponding to the value

Value of the 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.
hForwardOnly
This constant can only be used with Native Connectors.
Optimizes simple iterations that do not use the following features:
Reading the previous record.
Modifying a record.
Saving position.
If one of these features is used, the result may differ from the expected one.
For example, this constant can be used to populate a Table control programmatically.
hGeneric Generic search (see the Notes)
An exact-match search is performed by default (constant not specified).
hKeepFilter The filter set by <Source>.Filter will be taken into account, even if the search key is not optimized for the filter. Reminder: <Source>.Filter returns the optimized search key for the filter.
Caution: in this case, on large data files, performance problems may occur..
This variable cannot be used.
By default, the iteration performed after <Source>.ReadSeekFirst ignores the filter.
hLimitParsing The iteration will stop when the last search value is found or if no value matches the search.
The current record will correspond to this last record found.
<Source>.Found will return False and <Source>.Out will return True.
This constant is used to optimize search speed in Client/Server mode and on external databases (accessed via OLE DB or via Native Connectors).
hLockNo No blocking: the Record can be played back or modified by another application during playback.
This constant is not available.
JDBC access: This constant is not available.
hLockReadWrite Read/write lock: the record being 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.
This constant is not available.
JDBC access: This constant is not available.
hLockWrite Write lock: 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.
This constant is not available.
JDBC access: This constant is not available.
hNoRefresh
<Source>.ReadSeekFirst does not refresh the content of the table or query. If possible, the query is not re-run. All the saved positions are stored.
The management of locks is not available.
JDBC access: lock management is not supported for databases that are accessed through JDBC.
The lock options will have no effect if the locks are not supported by the OLE DB provider or by the Native Connector.
The lock mode specified by <Source>.ReadSeekFirst will remain effective during the calls to <Source>.ReadPrevious and <Source>.ReadNext.
To change the lock mode, use:
<Source>.ReadSeekFirst or <Source>.ReadSeekLast,
<Source>.ReadLast or <Source>.ReadFirst.

Remarks

Generic search/Exact-match search

Generic search (mainly for string fields): Finds all records beginning with the specified value.
For example: When performing a generic search for the string "Martin" in the NAME field, all records whose Name field begins with "Martin" will match the search. Therefore, the record that contains "Smither" will match the search (<Source>.Found returns True).
Note: For compatibility with WINDEV 5.5, the generic search for an empty string ("") is equivalent to using the <Source>.ReadFirst function.
Exact-match search: Finds all records exactly matching the specified value.
For example: When performing an exact-match search on the string "Martin" for the field NAME, function <Source>.Found returns True only for records where the heading is exactly "Martin".
Examples of searches on the CUSTOMER data file sorted by name:


Search value	Options	<Source>.ReadSeekFirst sets the position on the record.	<Source>.Found returns	<Source>.Out returns	Explanations
Davon		1	True	False	Davon exists. The end of data file was not reached yet.
Davo		1	False	False	Davo does not exist. Position on the first greater value (Davon). The end of data file was not reached yet.
Moor	hGeneric	8	True	False	Moor 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.
Moor		The record was not found (no move, the current record does not change).	False	False	Moor does not exist. The end of data file was not reached yet.
Norbert		The record was not found (no move, the current record does not change).	False	True	Norbert does not exist. Set to the first higher value (this value does not exist): the end of the data file is reached.

For more details, see the Hyper File 5.5 and 7: How are blank spaces handled in searches? table

Search performed on a key item or on a non-key item

The search can be performed on a key item or a non-key item.

If the search is performed on a key item:

the search is fast and the result is sorted.
if the iteration operation is continued by <Source>.ReadNext, the next records will correspond to the values greater than or equal to the search value. In this case, <Source>.Out must be checked after each read operation to find out whether the end of the data file has been reached.

If the search is performed on a non-key item:

the selected item will appear in red in the code editor and a warning will appear in the "Compilation errors" pane.
Note: The automatic completion only offers the key items.
if the iteration is continued by <Source>.ReadNext, the next records will correspond to the values equal to the search 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.
Use the <Source>.BuildKeyValue function.

1. Using a list of values

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

HReadSeekFirst(<File Name>, <Name of Composite Key>,
[<Search value of first element of composite key>,
<Search value of first element of composite key>, ...])

Example:

// Recherche de l'enregistrement
Client.LitRecherchePremier(Nom_Prénom, ["MOULIN", "Françoise"])

2. Using <Source>.BuildKeyValue

Example:

bufValRech is Buffer = Client.ConstruitValClé(Nom_Prénom, sNom, sPrénom)
Client.RecherchePremier(Nom_Prénom, bufValRech)
WHILE Client.Trouve()
	Client.Supprime()
	Client.Suivant(Nom_Prénom)
END

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 (<Source>.Filter), the filter is taken into account by the search only if the key used is identical.

To apply this filter in the rest of the iteration (even if the search key is not optimized for the filter), use the hKeepFilter constant.

If a filter is enabled, the filter is ignored by the search.

Looping through records that match a condition

In most cases, <Source>.ReadSeekFirst sets the position in the data file to loop through the records that match a condition. <Source>.ReadNext and <Source>.ReadPrevious are used to read the next and previous matching records.

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

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.

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 <Source>.UnlockRecNum.

Lock options will have no effect if the OLE DB provider or Native Connector (also called Native Access) does not support locks.

Optimizing iterations

To optimize the first iterations on a data file, use <Source>.Optimize on this data file.

Native XML Connector

The behavior of <Source>.ReadSeekFirst depends on <Source>.ActivateAutoFilter and <Source>.DeactivateAutoFilter.

<Source>.ActivateAutoFilter is enabled by default.

Therefore, to read the content of XML file, read the content of main file (the parent) then read the content of linked files (the children).

By default, when reading a file, a filter is automatically applied to the linked files in order to only read the records corresponding to the main file.

For example:

The email of this person can be retrieved when browsing the Person file.

To do so, simply set the position on the "Person" file and apply <Source>.ReadSeekFirst to the "Email" file.

In this case, the record read in the "Email" file will correspond to the first email associated with the current record in the "Person" file.

If this mechanism is disabled (<Source>.DeactivateAutoFilter), the record read in the "Email" file will correspond to the first record found in the Email file (and not to the child of the record read in the "Person" file).

Component: wd300hf.dll