- Browse item
- Browsing queries
- Native XML Connector
In french: HLitPremier
Not available with this kind of connection
Positions on the first file record according to a browse item. The record is read and the HFSQL variables are updated (Customer.Name for example, which means the Name
item of Customer
Values in the browse item are read in ascending order (see remarks
for more details).
In most cases, HReadFirst
is used to set the position in the data file in order to perform a read loop with HReadNext
Several cases may occur after the call to HReadFirst:
- the data file is empty or no record corresponds to the filter (defined by HFilter): no reading is performed and HOut returns True.
- the function tries to read a record that is already locked in read mode: no read operation is performed, HErrorLock returns True and HOut returns True.
The management of locks is not available.
This function can be used with the data files, HFSQL views or queries.
WHILE HOut(Customer) = False
// Process the record
<Result> = HReadFirst([<Data file> [, <Browse item>] [, <Options>]])
- False if an error occurred. In this case, HError returns an integer other than 0. HErrorInfo returns more details about the error. The record is not read.
- the value of HFound in the other cases (the record can be read, even if <Result> returns False).
<Data file>: Optional character string
Name of data file, HFSQL view or query used. If this parameter is an empty string (""), HReadFirst manipulates the last data file used by the last HFSQL function (function starting with "H").
<Browse item>: Optional character string
Name of item used to loop through the data file or view (this parameter is ignored by the queries). If this name is not specified, HReadFirst will use:
- For a data file: the last browse item used on this 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.
- For a query: the ORDER BY of query if it exists, otherwise the last item used.
- For a view: the sort item of the view (if it exists), otherwise the last item used.
<Options>: Optional constant
Used to configure:
- the lock set on the record read by HReadFirst
- whether the filter that was defined must be taken into account.
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.
|hKeepFilter||The 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 issues may arise for large files.
This constant cannot be used.
|hLockNo||No lock: the record can be read or modified by another application during the reading.|
This constant is not available.
|hLockReadWrite||Lock in read/write: the record currently read cannot be read or modified by another application.|
Lock in write-only. Operating mode equivalent to the hLockWrite
This constant is not available.
|hLockWrite||Lock in write mode: the record currently read can be read by another application but it cannot be modified by another application.|
This constant is not available.
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 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 HReadFirst
will remain effective during the calls to HReadPrevious
To modify the lock mode, you must use:
For Native Oracle Connector, a different lock mode can be specified for each record. However, if a transaction was started by SQLTransaction
before setting the lock, the lock will only be released at the end of the transaction (SQLTransaction
with the sqlCommit
The lock options are ignored. Use locking read functions (HReadFirstLock
) kept for backward compatibility.
The lock options are not available.
If the browse item is a key, HReadFirst reads the record with the lowest key value. The sort order is the one that was specified in the analysis for this key. If duplicates are found, HReadFirst reads the first "duplicate" record according to the sequence of record numbers.
If the browse item is not a key, HReadFirst
reads the first active record. When browsing the file, the records will be sorted according to their record number.
In this case, the selected browse item will appear in red in the code editor and a warning will be displayed in the "Code" pane
By default, HReadFirst re-executes the query to refresh the result. To avoid re-executing the query, we recommend that you use the hNoRefresh constant.
Browsing a query run with the hQueryWithoutCorrection constant:
To browse the records in the order returned by the database, there is no need to specify a browse item. Example:
If a browse item is specified, the query result is retrieved and indexed in its entirety. The iteration is performed on the specified item. The initial sort of the query (specified by ORDER BY) is ignored. The created index (in HFSQL format) is sensitive to the case, to the punctuation, to the accented characters and in ascending order.
HReadFirst(MyQuery, MyItem, hNoRefresh)
The created index is used to perform searches on the query result.
The memos associated with the record can be automatically read (or not) when reading the record. HSetMemo
is used to customize this automatic read operation.
If the memos are supported, the associated text memos are read when the record is read. The binary memos are read only when they are explicitly used (HExtractMemo
is the first function that handles the specified data file, the password is checked when the opening data file. If the password is incorrect, HErrorPassword
Native XML Connector
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).
When reading a data file, a filter is automatically applied to the linked data files in order to only read the records corresponding to the main file.
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 HReadFirst 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 (HDeactivateAutoFilter
), 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).
- The current record number is returned by HRecNum.
- HChangeKey is used to modify the search key while remaining positioned on the current record.
- To improve the first browse times on a file, use HOptimize on this data file.
- This function replaces HReadFirstLock and HReadFirstNoLock, which were kept for compatibility with WINDEV 5.5.
This page is also available for…