ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Help / WLanguage / Managing databases / HFSQL / HFSQL functions
  • Managing automatic identifiers
  • Reusing the deleted or freed records
  • Version of data file after an addition
  • Adding a record into a query
  • Adding records into a view
  • Browsing and adding records
  • Slowness when adding or deleting a record for the first time in an HFSQL data file
  • Addition into a database in Hyper File 5.5 format
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
Duplicates the record read in a data file: the record found in memory is added into the data file (query or view). The indexes corresponding to all the keys used in the data file are automatically updated. The possible memos are added if the management of memos is enabled (HSetMemo).
After the call to HDuplicateRecord:
  • An automatic management of errors is available for several types of errors: Duplicate error, integrity error, password error, modification conflict error and status error during modification conflict, lock error, ... For more details, see Assisted HFSQL error handling.
  • If the management of duplicates is enabled and if the data file contains a unique key, HErrorDuplicates returns True if the value of added key is not unique. The record is not added.
  • The added record becomes the current record. The automatic identifier is automatically filled. By default, the current iteration is not affected.
Remark: The entire record in memory (the content of record previously read) is written into the data file.
Remarks:
  • This function can also be used on a view or on a query.
  • HDuplicateRecord and HAdd are equivalent.
Example
// Duplicates the current record
HDuplicateRecord(Customer)
Syntax
<Result> = HDuplicateRecord([<Data file> [, <Options>]])
<Result>: Boolean
  • True if the record was added,
  • False if a problem occurred (integrity error, duplicate error, ...). HError is used to identify the error.
<Data file>: Optional character string
Name of the data file, view or query used. If this name is not specified, HDuplicateRecord will use the last data file used by the last HFSQL function (function starting with "H").
<Options>: Optional constant
Used to configure:
  • the effect of addition on the current browse.
  • the mode for calculating the automatic identifier. For more details, see Managing the automatic identifier during an addition.
  • the lock mode applied to the added record.
    • Java Access by JDBC: The management of locks is not available for databases accessed by JDBC.
  • the management of duplicates.
  • the management of integrity.
Hyper File 5.5 This parameter is ignored.
hAffectBrowseEffect of addition on the browse: The addition affects the browse.
For example, HReadNext used after HDuplicateRecord positions on the record found after the added record.
The hAffectBrowse constant has priority over the hWriteDefault constant.
hCheckDuplicatesManagement mode of duplicates: Checks for duplicates for this operation, even if the duplicate check is disabled (HSetDuplicates).
A WLanguage error occurs if the hIgnoreDuplicates and hCheckDuplicates constants are used at the same time.
Java Access by JDBC: This constant is not available.
hCheckIntegrityManagement mode of integrity: Checks the integrity for the operation, even if the automatic integrity check is disabled (HSetIntegrity).
A WLanguage error occurs if the hIgnoreIntegrity and hCheckIntegrity constants are used at the same time.
Java Access by JDBC: This constant is not available.
hForceIDAutoMode for calculating the automatic identifier: The automatic identifier is not calculated during the addition. The identifier corresponds to:
  • the value assigned to the item through programming (CUSTOMERID = 7 for example)
  • the default identifier value specified in the data model editor (if the data file was just opened, with no record read)
  • the identifier value found in memory (identifier value for the last record read in the data file).
Once the record is added, the next automatic identifier calculated by the HFSQL engine will be calculated while ignoring the value added by hForceIDAuto.
A WLanguage error occurs if the hSetIDAuto and hForceIDAuto constants are used at the same time.
Native Connectors (Native Accesses) SQLServer CE: The hForceIDAuto constant cannot be used.
hIgnoreDuplicatesManagement mode of duplicates: Does not check for duplicates for this action, even if the automatic duplicate check is enabled (HSetDuplicates).
A WLanguage error occurs if the hIgnoreDuplicates and hCheckDuplicates constants are used at the same time.
Java Access by JDBC: This constant is not available.
hIgnoreIntegrityManagement mode of integrity: Ignores the integrity check for this add operation, even if the automatic integrity check is enabled (HSetIntegrity).
A WLanguage error occurs if the hIgnoreIntegrity and hCheckIntegrity constants are used at the same time.
Java Access by JDBC: This constant is not available.
hLockNo (default value)Lock mode applied to the added record: No lock: the added record will not be locked.
Java Access by JDBC: This constant is not available.
hLockReadWriteLock mode applied to the added record: Lock in read/write: the added record will be locked in read/write. This record cannot be read or modified by another application. Only the current application can modify it, read it or unlock it.
Java Access by JDBC: This constant is not available.
hLockWriteLock mode applied to the added record: Lock in write mode: the added record will be locked in write mode. This record can be read by another application but it cannot be modified by another application. Only the current application can modify it or unlock it.
Java Access by JDBC: This constant is not available.
hSetIDAutoMode for calculating the automatic identifier: The automatic identifier is not calculated during the addition: the identifier value will be the one stored during the addition.
The next identifier value calculated by the HFSQL engine will correspond to the greatest identifier value in the file +1.
A WLanguage error occurs if the hSetIDAuto and hForceIDAuto constants are used at the same time.
Native Connectors (Native Accesses) SQLServer CE: The hSetIDAuto constant cannot be used.
hWriteDefault
(default value)
Effect of addition on the browse: The addition does not affect the current browse.
For example, HReadNext used after HDuplicateRecord positions on the record found after the current record before the addition.
The hAffectBrowse constant has priority over the hWriteDefault constant.
Remarks

Managing automatic identifiers

By default, the "automatic identifier" item is automatically updated when a record is added into a data file. There is no need to read the record again to find out the value of the automatic identifier. Simply use the following syntax: <File name>.<Name of automatic identifier item>.
The hForceIDAuto and hSetIDAuto constants are used to modify the default behavior of the automatic identifier.
For more details on automatic identifiers for new records, see Managing the automatic identifier during an addition.
JavaOLE DBNative Connectors (Native Accesses) Special case
  • If the database generates an automatic identifier, the HFSQL engine keeps this value. If the hForceIDAuto or hSetIDAuto constant is specified, the HFSQL engine replaces the generated value by the desired value.
    Remark: the hForceIDAuto constant is equivalent to hSetIDAuto: the automatic identifier calculated by the HFSQL engine during the next addition will be unique in the data file.
  • If no automatic identifier is generated by the database, the HFSQL engine generates the value and assigns it to the automatic identifier.
WINDEVUniversal Windows 10 AppJavaHFSQL ClassicHFSQL Client/ServerHyper File 5.5

Reusing the deleted or freed records

When adding a new record, the HFSQL engine optimizes the filling of the data file. The space corresponding to the deleted or freed records is used first when a new record is added.
The crossed records are not re-used.
WINDEVUniversal Windows 10 AppJavaHFSQL ClassicHFSQL Client/ServerHyper File 5.5

Version of data file after an addition

If the record was added to the data file (no duplicate error and no integrity error), the version number of the data file is modified. To get the version number, use HVersion.

Adding a record into a query

Adding a record into a query can be performed:
  • in the query result.
  • in the data files handled by the query (hModifyFile constant used in HExecuteQuery or HExecuteSQLQuery). In this case, the hWithFilter constant is automatically selected.
Regardless of the runtime mode of the query (with or without the hWithFilter constant), adding records into a query is allowed for the single-file queries only. The calculated items specified during the addition are ignored. They are automatically calculated.
Caution:
  • No addition is allowed in a query that uses groups or aggregates.
  • The management of integrity and duplicates is not performed during the operations on the multi-file queries: it is recommended to use transactions to avoid any problems.
WINDEVUniversal Windows 10 AppHFSQL ClassicHFSQL Client/Server

Adding records into a view

You have the ability to add records into a view created on data files in HFSQL Classic format. These records are added in memory only. To add them into the data file linked to the view (simple view for example), you must use HViewToFile.

Browsing and adding records

You can configure the effect of adding a record during the browse of a data file (hWriteDefault and hAffectBrowse constants). The operating mode of the earlier versions can be kept by using the hAffectBrowse constant.
JavaOLE DBNative Connectors (Native Accesses) Special cases: If the record is added during a browse, it will be visible in the current browse only. If other browse operations have been defined on this database, the new record will only be visible once these browse operations have been reinitialized.

Slowness when adding or deleting a record for the first time in an HFSQL data file

Accessing a record in an HFSQL data file for the first time may take long. To fix this problem:
  • Disable the antivirus for .FIC,.NDX,.MMO and.REP files.
  • Disable the "Restore the system" option in Windows XP.
WINDEVHyper File 5.5

Addition into a database in Hyper File 5.5 format

If you are using HDuplicateRecord with a database in Hyper File 5.5 format:
  • The add options (<Options>) are ignored.
  • The TEXT items are automatically filled with space characters.
  • HDuplicateRecord cannot be used on a view created from Hyper File 5.5 data files.
Component: wd290hf.dll
Minimum version required
  • Version 18
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 05/26/2022

Send a report | Local help