PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US

  • Managing automatic identifiers
  • Re-using 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 problem during the first addition or during the first deletion performed in a 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/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Adds:
  • the record found in memory into the data file (query or view).
  • Versions 19 and later
    WINDEVWEBDEV - Server codeWindows Mobile the record found in a Record variable into the data file (query or view).
    New in version 19
    WINDEVWEBDEV - Server codeWindows Mobile the record found in a Record variable into the data file (query or view).
    WINDEVWEBDEV - Server codeWindows Mobile the record found in a Record variable into the data file (query or view).
    WINDEVWEBDEV - Server codeAndroidAndroid Widget Windows Mobile the record found in a Record variable 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 HAdd:
  • An automatic management of errors is proposed for several types of errors: Duplicate error, integrity error, password error, modification conflict error and status error during modification conflict, lock error, ... See Assisted management of HFSQL errors for more details.
  • 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 browse is not affected.
Note: The entire record in memory is written into the data file with the values that were assigned to it (otherwise, the content of record previously read). To clear the values from the record in memory, all you have to do is use HReset.
Versions 15 and later
Android This function is now available for the Android applications.
New in version 15
Android This function is now available for the Android applications.
Android This function is now available for the Android applications.
Versions 17 and later
iPhone/iPad This function is now available for the iPhone/iPad applications.
New in version 17
iPhone/iPad This function is now available for the iPhone/iPad applications.
iPhone/iPad This function is now available for the iPhone/iPad applications.
Versions 18 and later
Android Widget This function is now available in Android Widget mode.
Universal Windows 10 App This function is now available in Windows Store apps mode.
New in version 18
Android Widget This function is now available in Android Widget mode.
Universal Windows 10 App This function is now available in Windows Store apps mode.
Android Widget This function is now available in Android Widget mode.
Universal Windows 10 App This function is now available in Windows Store apps mode.
Versions 21 and later
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
New in version 21
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Versions 23 and later
AndroidAndroid Widget The syntax for handling a Record variable is now available.
New in version 23
AndroidAndroid Widget The syntax for handling a Record variable is now available.
AndroidAndroid Widget The syntax for handling a Record variable is now available.
Note: From version 19, HFSQL is the new name of HyperFileSQL.
// Add a record into a file
// (record described by programming)
Customer.LastName = "Clark"
Customer.FirstName = "Vince"
Customer.Address = "Palm Lane"
Customer.City = "Philadelphia"
Customer.Zip = "19101"
Customer.Country = "USA"
HAdd(Customer)
WINDEVAndroidAndroid Widget iPhone/iPadWindows MobileUniversal Windows 10 AppJavaHFSQLHFSQL Client/ServerStored proceduresHyper File 5.5OLE DBNative Accesses
// Add a record entered in a window
// into Customer file
ScreenToFile()
HAdd(Customer)
Syntax

Adding the record found in memory into a data file Hide the details

<Result> = HAdd([<File Name> [, <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.
<File Name>: Optional character string (with or without quotes)
Name of data file, view or query used. If this name is not specified, HAdd handles the last data file used by the last function for HFSQL management (starting with the letter H).
<Options>: Optional constant
Used to configure:
  • the effect of addition on the current browse.
  • the mode for calculating the automatic identifier. See Managing the automatic identifier during an addition for more details.
  • the lock mode applied to the added record.
    • Windows Mobile The record lock is available for the HFSQL Client/Server data files and for the data files handled by Native Access. A HFSQL Mobile record cannot be locked. This limit is due to the operating system of Pocket PC.
    • PHP The management of locks is not available in PHP.
    • Versions 15 and later
      AndroidAndroid Widget The management of locks is not available for the SQLite databases.
      New in version 15
      AndroidAndroid Widget The management of locks is not available for the SQLite databases.
      AndroidAndroid Widget The management of locks is not available for the SQLite databases.
    • Java Access by JDBC: The management of locks is not available for the 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 HAdd positions on the record found after the added record.
The hAffectBrowse constant has priority over the hWriteDefault constant.
hLockNo (default value)Lock mode applied to the added record: No lock (even if HStartLock was used): the added record will not be locked.
AndroidAndroid Widget PHP This constant is not available.
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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Pocket PC.
AndroidAndroid Widget PHP This constant is not available.
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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Pocket PC.
AndroidAndroid Widget PHP This constant is not available.
Java Access by JDBC: This constant is not available.
hWriteDefault
(default value)
Effect of addition on the browse: The addition does not affect the current browse.
For example, HReadNext used after HAdd positions on the record found after the current record before the addition.
The hAffectBrowse constant has priority over the hWriteDefault constant.
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 Accesses SQLServer CE: The hSetIdAuto constant cannot be used.
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 by 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 Accesses SQLServer CE: The hForceIdAuto constant cannot be used.
hIgnoreDuplicatesManagement mode of duplicates: Ignores the duplicate check for this operation, 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.
AndroidAndroid Widget PHP This constant is not available.
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.
AndroidAndroid Widget PHP This constant is not available.
Java Access by JDBC: This constant is not available.
hCheckDuplicatesManagement mode of duplicates: Checks the 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.
AndroidAndroid Widget PHP This constant is not available.
Java Access by JDBC: This constant is not available.
hCheckIntegrityManagement mode of integrity: Checks the integrity of 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.
AndroidAndroid Widget PHP This constant is not available.
Java Access by JDBC: This constant is not available.
Versions 19 and later
WINDEVWEBDEV - Server codeAndroidAndroid Widget Windows Mobile

Adding the content of Record variable into a data file Hide the details

<Result> = HAdd(<File Name> , <Record> [, <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.
<File Name>: Character string (with or without quotes)
Name of data file, view or query used.
<Record>: Record variable
Name of the Record variable containing the different values of items.
<Options>: Optional constant
Used to configure:
  • the effect of addition on the current browse.
  • the mode for calculating the automatic identifier. See Managing the automatic identifier during an addition for more details.
  • the lock mode applied to the added record.
    Windows Mobile The record lock is available for the HFSQL Client/Server data files and for the data files handled by Native Access. A HFSQL Mobile record cannot be locked. This limit is due to the operating system of Pocket PC.
  • 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 HAdd positions on the record found after the added record.
The hAffectBrowse constant has priority over the hWriteDefault constant.
hLockNo
(default value)
Lock mode applied to the added record: No lock (even if HStartLock was used): the added record will not be locked.
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget This constant is not available.
hWriteDefault
(default value)
Effect of addition on the browse: The addition does not affect the current browse.
For example, HReadNext used after HAdd positions on the record found after the current record before the addition.
The hAffectBrowse constant has priority over the hWriteDefault constant.
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 Accesses SQLServer CE: The hSetIdAuto constant cannot be used.
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 by 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 Accesses SQLServer CE: The hForceIdAuto constant cannot be used.
hIgnoreDuplicatesManagement mode of duplicates: Ignores the duplicate check for this operation, 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.
AndroidAndroid Widget 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.
AndroidAndroid Widget This constant is not available.
hCheckDuplicatesManagement mode of duplicates: Checks the 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.
AndroidAndroid Widget This constant is not available.
hCheckIntegrityManagement mode of integrity: Checks the integrity of 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.
AndroidAndroid Widget This constant is not available.
New in version 19
WINDEVWEBDEV - Server codeAndroidAndroid Widget Windows Mobile

Adding the content of Record variable into a data file Hide the details

<Result> = HAdd(<File Name> , <Record> [, <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.
<File Name>: Character string (with or without quotes)
Name of data file, view or query used.
<Record>: Record variable
Name of the Record variable containing the different values of items.
<Options>: Optional constant
Used to configure:
  • the effect of addition on the current browse.
  • the mode for calculating the automatic identifier. See Managing the automatic identifier during an addition for more details.
  • the lock mode applied to the added record.
    Windows Mobile The record lock is available for the HFSQL Client/Server data files and for the data files handled by Native Access. A HFSQL Mobile record cannot be locked. This limit is due to the operating system of Pocket PC.
  • 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 HAdd positions on the record found after the added record.
The hAffectBrowse constant has priority over the hWriteDefault constant.
hLockNo
(default value)
Lock mode applied to the added record: No lock (even if HStartLock was used): the added record will not be locked.
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget This constant is not available.
hWriteDefault
(default value)
Effect of addition on the browse: The addition does not affect the current browse.
For example, HReadNext used after HAdd positions on the record found after the current record before the addition.
The hAffectBrowse constant has priority over the hWriteDefault constant.
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 Accesses SQLServer CE: The hSetIdAuto constant cannot be used.
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 by 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 Accesses SQLServer CE: The hForceIdAuto constant cannot be used.
hIgnoreDuplicatesManagement mode of duplicates: Ignores the duplicate check for this operation, 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.
AndroidAndroid Widget 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.
AndroidAndroid Widget This constant is not available.
hCheckDuplicatesManagement mode of duplicates: Checks the 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.
AndroidAndroid Widget This constant is not available.
hCheckIntegrityManagement mode of integrity: Checks the integrity of 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.
AndroidAndroid Widget This constant is not available.
WINDEVWEBDEV - Server codeAndroidAndroid Widget Windows Mobile

Adding the content of Record variable into a data file Hide the details

<Result> = HAdd(<File Name> , <Record> [, <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.
<File Name>: Character string (with or without quotes)
Name of data file, view or query used.
<Record>: Record variable
Name of the Record variable containing the different values of items.
<Options>: Optional constant
Used to configure:
  • the effect of addition on the current browse.
  • the mode for calculating the automatic identifier. See Managing the automatic identifier during an addition for more details.
  • the lock mode applied to the added record.
    Windows Mobile The record lock is available for the HFSQL Client/Server data files and for the data files handled by Native Access. A HFSQL Mobile record cannot be locked. This limit is due to the operating system of Pocket PC.
  • 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 HAdd positions on the record found after the added record.
The hAffectBrowse constant has priority over the hWriteDefault constant.
hLockNo
(default value)
Lock mode applied to the added record: No lock (even if HStartLock was used): the added record will not be locked.
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget 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.
Windows Mobile This constant is available for HFSQL Client/Server and for Native Accesses. This constant is not available for HFSQL Mobile. Indeed, no record can be locked. This limit is due to the operating system of Mobile Device (Pocket PC).
AndroidAndroid Widget This constant is not available.
hWriteDefault
(default value)
Effect of addition on the browse: The addition does not affect the current browse.
For example, HReadNext used after HAdd positions on the record found after the current record before the addition.
The hAffectBrowse constant has priority over the hWriteDefault constant.
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 Accesses SQLServer CE: The hSetIdAuto constant cannot be used.
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 by 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 Accesses SQLServer CE: The hForceIdAuto constant cannot be used.
hIgnoreDuplicatesManagement mode of duplicates: Ignores the duplicate check for this operation, 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.
AndroidAndroid Widget 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.
AndroidAndroid Widget This constant is not available.
hCheckDuplicatesManagement mode of duplicates: Checks the 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.
AndroidAndroid Widget This constant is not available.
hCheckIntegrityManagement mode of integrity: Checks the integrity of 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.
AndroidAndroid Widget This constant is not available.
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. All you have to do is 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.
AndroidAndroid Widget JavaPHPOLE DBNative 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 requested value.
    Note: 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.
WINDEVWEBDEV - Server codeiPhone/iPadWindows MobileUniversal Windows 10 AppJavaPHPAjaxExternal languageHFSQLHFSQL Client/ServerStored proceduresHyper File 5.5

Re-using 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.
WINDEVWEBDEV - Server codeiPhone/iPadWindows MobileUniversal Windows 10 AppJavaPHPAjaxExternal languageHFSQLHFSQL Client/ServerStored proceduresHyper 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 find out 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 is using the groups or the 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.
WINDEVWEBDEV - Server codeiPhone/iPadWindows MobileUniversal Windows 10 AppAjaxExternal languageHFSQLHFSQL Client/ServerStored procedures

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 have the ability to configure the effect of record addition 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).
JavaPHPOLE DBNative Accesses Special cases
If the addition is performed during a browse, the new record 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 re-initialized.

Slowness problem during the first addition or during the first deletion performed in a HFSQL data file

An unexpected slowness problem may occur during the first access to a record found in a HFSQL data file. To fix this problem:
  • Disable the anti-virus program for the .FIC, .NDX, .MMO and .REP files.
  • Disable the "Restore the system" option in Windows XP.
WINDEVWEBDEV - Server codeAjaxExternal languageStored proceduresHyper File 5.5

Addition into a database in Hyper File 5.5 format

If you are using HAdd with a database in Hyper File 5.5 format:
  • The add options (<Options>) are ignored.
  • The TEXT items are automatically filled with space characters.
  • HAdd cannot be used with a view created on data files in Hyper File 5.5 format.
Components
WINDEVWEBDEV - Server code wd230hf.dll
Windows Mobile wp230hf.dll
Java wd230java.jar
Linux wd230hf.so
Android wd230android.jar
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment