Regardless of the platform used, the data saved in the HFSQL files is in ANSI format.On a UNICODE platform (Pocket PC for example), HBuildKeyValueANSI is used to build the value of a composite key in order to save this composite key in a HFSQL Mobile data file.
On an ANSI platform (PC for example), this function is equivalent to
HBuildKeyValue.
HBuildKeyValueANSI must not be used to:
Reminder: The composite keys are binary strings whose content cannot be displayed directly. See
Composite keys for more details.
Versions 18 and later
New in version 18Versions 21 and later New in version 21 Remark: From version 19, HFSQL is the new name of HyperFileSQL.
// Assign an item to a linked file
Invoice.CustLastNameFirstName = HBuildKeyValueANSI(Customer, ...
CustLastNameFirstName, Customer.LastName, Customer.FirstName)
Syntax
<Result> = HBuildKeyValueANSI(<Data file> , <Composite key> , <Value of components>)
<Result>: Character string
Value of the composite key that must be saved in the data file.
<Data file>: Character string (with or without quotes)
Name of HFSQL data file used.
<Composite key>: Character string (with or without quotes)
Name of the item corresponding to the composite key.
<Value of components>: Character string (with quotes)
Value that will be assigned to each component of the composite key.
This parameter has the following format: <Component 1> , <Component 2>, ...,<Component N>.
For example: "MOORE", "Vince".
Business / UI classification: Business Logic