Home | Sign in | English EN

This content has been translated automatically. Click here to view the French version.
  • Handling a crossed record
  • Number of crossed records
  • Version of data file
  • Crossing a record from a query
  • Special cases
  • xBase files
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
Crosses a record in a data file. The record is deleted logically and it can be retrieved if necessary.
The following operations are performed:
  • the record becomes inactive. The data is stored (which is not the case when a record is deleted by HDelete).
  • the indexes (corresponding to the record keys) are deleted from the index file.
  • the memos associated with the record are stored.
This function can be used on the data files, the HFSQL Mobile views or the queries.
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
// Raye l'enregistrement numéro 123
HCross(Client, 123)
// Suppression (rayure) des commandes d'un client
HReadSeekFirst(COMMANDE, NUMCLI, ValNumCli)
WHILE HFound() = True
<Result> = HCross([<Data file> [, <Record number> [, <Options>]]])
<Result>: Boolean
  • True if the record was crossed,
  • False if an error occurred (locked record, integrity error, ...). HErrorInfo returns more details.
<Data file>: Optional character string
Name of HFSQL data file, query or view used.
If this parameter is an empty string (""), HCross manipulates the last data file used by the last HFSQL function (function starting with "H").
<Record number>: Optional integer
Number of the record to cross.
If this parameter is not specified (equal to 0 or to the hCurrentRecNum constant), the current record will be crossed.
<Options>: Optional constant
  • the lock mode applied to the crossed record. If no lock constant is specified, the crossed record is not locked.
    (default value)
    No lock: the crossed record will not be locked.
    hLockWriteLock in write mode: the current scratched record can be read and consulted (HRead function) by another application but cannot be reactivated by another application. Only the current application can re-enable it.
    hLockReadWriteLock in read/write: the current crossed record cannot be read or re-enabled by another application.
  • the integrity management applied to the crossed record.
    hIgnoreIntegrityIgnores the integrity check for this operation, even if the automatic integrity check is enabled (HSetIntegrity).
    hCheckIntegrityChecks the integrity for the operation, even if the automatic integrity check is disabled (HSetIntegrity).

    A WLanguage error occurs if the two constants are used at the same time. These constants have no effect on the cascading deletion.

Handling a crossed record

Number of crossed records

HNbRec is used to find out the number of crossed records in the data file.
Remark: For backward compatibility with WEBDEV 1.5/WINDEV 5.5, the number of crossed records can also be returned by the H.NbDel variable.

Version of data file

If the function HCrossis successful, the version number of the data file is changed. This version number is returned by HVersion.

Crossing a record from a query

A record can be crossed:
  • in the query result.
  • in the files handled by the query (hModifyFile constant used in HExecuteQuery or HExecuteSQLQuery). In this case, the hWithFilter constant is automatically selected.
Regardless of how the query is executed (with or without the hWithFilterconstant), the HCross function can only be used on single-file queries.
  • No record can be crossed in a query that is using the groups or aggregates.
  • The management of integrity and duplicates is not performed during the operations on the multi-file queries: we recommend that you use the transactions to avoid any problem.

Special cases

  • Managing locks:
    If a lock problem occurs when "crossing" a record (attempt to cross a record locked in write mode for example), the record is not modified and HErrorLock returns True.
  • Managing the referential integrity
    If the management of the referential integrity is enabled (HSetIntegrity) and if the integrity is not checked during the deletion, HCross is not run. HErrorIntegrity must be checked after HCross.
  • Deleted records
    HCross must not be called on a record that was deleted beforehand.
WEBDEV - Server codeNative Connectors (Native Accesses)

xBase files

HDelete and HCross have the same effect: the record is crossed but it is not deleted. Therefore, the record can be re-enabled by HModify. In this case, HState returns the hStateCrossed constant for a deleted record (instead of hStateDel).
Component: wd270hf.dll
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment