Managing the Unicode format in the HFSQL files

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Access via ODBC or OLE DB

Big Data

HFSQL functions

Handling a CEDB database

Management of 3-tier

Management of HFSQL Client/Server

Management of HFSQL Cluster

Management of log process

Management of replication

Management of statistics

Management of transactions

Management of triggers

Management of xBase files

SQL functions

Managing the Unicode format in the HFSQL files

Overview

How to proceed?

For information

Accessing the databases: summary

Analysis shared between earlier WINDEV applications and WINDEV 24 applications

Assisted management of HFSQL errors

Automatic modification of data files

Automatic modification of data files: new date format

Browsing the HFSQL data files

Communication by GPRS

Connecting to a database via RPC

Errors while managing data files

Filtering a data file, a view or a query

Functions for HFSQL management

HFSQL data files exceeding 2 gigabytes

HFSQL in network mode on a server running Windows NT4, 2000, XP or 2003

HFSQL management functions (prefixed syntax)

HFSQL thumbnails

HFSQL: Change of name

Hyper File functions available for backward compatibility

Locking data files: correspondence between WINDEV 5.5 and the later versions

Management errors specific to Native Accesses

Managing NULL in HFSQL

Managing aliases on the data files

Managing connections

Managing space characters in the searches?

Managing the Unicode format in the HFSQL files

Managing the automatic identifiers when adding a record

Modifying the query content

Native Access access

Native XML Access

Optimizing the remote access

Partial indexing of memos

Remote access (RPC on HFSQL)

SQL functions: Special case

Search and full-text index

Synchronizing data (Windows CE)

The .REP file

The HFSQL views

The composite keys

The different types of browse available in SQL

Unalterable data files

WDModFic : Tool for automatic modification of data files

Overview
How to proceed?
Creating a Unicode item in the analysis
Switching from Unicode to ANSI (and conversely) in the data model editor
For information
Controls linked to the items
Programming in WLanguage
Search performed by HReadSeek

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

Managing the Unicode format in the HFSQL files

Not available with these kinds of connection

Overview

The analysis proposes two types of Unicode items:

"Unicode Text" item
"Unicode Memo" item.

These items are used to store information in Unicode format.

These items can be associated with a language: the sort performed on the item will take the specified language into account. The association with the language can be done:

in the data model editor.
by programming via the H.LanguageCreationUnicode variable. This variable must be used before creating the data files (HCreation ou HCreationIfNotFound).

The texts entered in the Unicode items are automatically supported by the different controls found in the window or in the page, the tables, ...

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

How to proceed?

Creating a Unicode item in the analysis

When creating the item in the data model editor (see Operations on the items for more details), all you have to do is specify the requested sub-type for the item. A Text item can be:

A string (corresponds to an Ansi character string)
A character
Unicode (corresponds to a Unicode character string)
Text memo (corresponds to an Ansi text memo)
Unicode text memo (corresponds to a Unicode text memo).

When selecting a Unicode type (string or text memo), the data model editor allows you to specify the characteristics of the language that will be entered in this item.

These characteristics are required to perform the sort on the item.

If a language is selected, this language will be used to perform the sorts on the current item. An linguistic sort will be performed. The sort is performed according to the following order:
1. Sort performed on the entire string.
2. Taking the accented characters into account.
3. Taking the uppercase characters into account.
If the "Language" option corresponds to "< Defined at creation >", you have the ability to specify the characteristics of the language by programming via the H.LanguageCreationUnicode variable. This variable must be used before creating the data files (HCreation or HCreationIfNotFound). Therefore, the same analysis can be used to manage several Unicode languages.
Versions 17 and later
If the "Language" option corresponds to "<Binary sort>", the sort will be performed by comparing the binary value of the bytes. This type of sort is very fast. It should be used to perform an exact-match search for example.
New in version 17
If the "Language" option corresponds to "<Binary sort>", the sort will be performed by comparing the binary value of the bytes. This type of sort is very fast. It should be used to perform an exact-match search for example.
If the "Language" option corresponds to "<Binary sort>", the sort will be performed by comparing the binary value of the bytes. This type of sort is very fast. It should be used to perform an exact-match search for example.
Versions 17 and later
If the "Language" option corresponds to "<Fast sort (multilingual)>", a comparison will be performed character by character according to a generic sort. The same sort will be performed, regardless of the characters found in the item.
New in version 17
If the "Language" option corresponds to "<Fast sort (multilingual)>", a comparison will be performed character by character according to a generic sort. The same sort will be performed, regardless of the characters found in the item.
If the "Language" option corresponds to "<Fast sort (multilingual)>", a comparison will be performed character by character according to a generic sort. The same sort will be performed, regardless of the characters found in the item.

Switching from Unicode to ANSI (and conversely) in the data model editor

The sub-type of an item can be modified by switching it from ANSI to Unicode (and conversely). In this case, an automatic data modification will be performed.

The conversion from ANSI to Unicode will be performed according to the specified language.

The conversion from Unicode to ANSI will be performed according to the current language.

For information

Controls linked to the items

When the controls are created (in a window or in a page), you have the ability to specify whether the control supports the Unicode format or not (check "Unicode" in the "General" tab of the description window of the control).

When creating the controls linked to a Unicode item, "Unicode" is automatically checked in the control description.

..Unicode is used to find out and specify whether the value of a control is a Unicode string.

Programming in WLanguage

The method for programming the files containing Unicode items is identical to the method for programming the files containing ANSI items. The language options defined in the data model editor are taken into account during the indexed browses and during the sorts to define the order of records.

..Type is used to find out whether an item is a Unicode item or an Ansi item.

Search performed by HReadSeek

No generic search should be performed on the Unicode items that are case sensitive. Indeed, the coding of characters being specific in Unicode, this type of search may return invalid or incomplete results.