PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
  • Specific features of the Native SQL Server Connector
  • Browsing Table control loaded in memory
  • Locking a data file (table) in a transaction
  • Record number
  • Retrieving the DATETIME types
  • Options of the analysis
  • Array items
  • Encryption via SSL
  • Stored procedures
  • Default values of items
  • Specific features for the HFSQL functions
  • Operating problems
  • Special case: SQL Azure
  • Managing calculated items
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
Native SQL Server Connector: Specific features and remarks
Overview
The following paragraphs present the main remarks and the specific features of Native SQL Server Connector.
Specific features of the Native SQL Server Connector

Browsing Table control loaded in memory

The new records added into a browsing Table control loaded in memory cannot be modified straightaway. To modify these new records directly in the Table control, you must use TableDisplay with the taInit constant after the additions.

Locking a data file (table) in a transaction

HLockFile starts a transaction and locks the table in Exclusive mode. HUnlockFile validates the transaction and unlocks the table.

Record number

You cannot specify a record number other than zero in HWrite and HRead. Indeed, "zero" corresponds to the current record number.
Similarly, HLockRecNum and HUnlockRecNum can only be used on the current record.

Retrieving the DATETIME types

  • The precision of values read and written is limited to the WLanguage precision : the millisecond.
    Special case: The datetime type: The precision is limited by SQLServer to 0.00333 second.
  • The new SQLServer 2008 date and time types are supported only from SQLnCLI for SQL Server 2008.. For earlier client layers, these items are considered as "unicode text" items.

Options of the analysis

  • No matter whether the options ("Case sensitive", "Accent sensitive" and "Punctuation sensitive") are checked in the data model editor, the search will always be sensitive to the case, to the accented characters and to the punctuation.
  • The analysis options regarding the full-text indexes are not supported by the Native Connector.
  • The analysis options regarding the partial indexing of text memos are not supported by the Native Connector.

Array items

The array items are not supported by the Native Connector. If you are using an array item, only the value of subscript 1 in the array will be handled by the HFSQL functions (in read/write).

Encryption via SSL

The encryption by SSL (Secure Socket Layer) is not supported in this version.

Stored procedures

Limit: HPrepareSQLQuery cannot be used to prepare a stored procedure that returns:
  • records.
  • columns.
You must use HExecuteSQLQuery.
Versions 21 and later

Default values of items

The default values of items are managed by the Native SQL Server Connector. The default values can be:
  • a value,
  • an SQL formula. In this case, the SQL expression must be recognized by the HFSQL engine and by the SQL Server database.
New in version 21

Default values of items

The default values of items are managed by the Native SQL Server Connector. The default values can be:
  • a value,
  • an SQL formula. In this case, the SQL expression must be recognized by the HFSQL engine and by the SQL Server database.

Default values of items

The default values of items are managed by the Native SQL Server Connector. The default values can be:
  • a value,
  • an SQL formula. In this case, the SQL expression must be recognized by the HFSQL engine and by the SQL Server database.

Specific features for the HFSQL functions

The specific features for using the HFSQL functions with Native SQL Server Connector are as follows:
Specific featuresAffected functions
The hDistinct constant is ignored: all the records (including the duplicates) will be browsed.HForward, HBackward
HReadPrevious, HReadNext
HPrevious, HNext
Multi-file query
HAdd, HModify and HDelete are not supported.
HAdd, HModify
HDelete
If a duplicate error occurs on HModify, HRead (with the hCurrentRecNum constant) does not read the requested record.
This problem will be fixed in a forthcoming version.
HRead
The hForceIdAuto constant is ignored by HModify. An "IDENTITY" column cannot be modified in SQL Server.HModify
The lock options of the read functions (HReadSeek, etc.) are ignored.Read functions (HReadFirst, etc.)
A record locked by HLockRecNum is unlocked when it is read again.Read functions (HReadFirst, etc.)
HCreation creates DATE and TIME items if the version of the server and the client layer correspond to SQL Server 2008 (or later).HCreation

Operating problems

When using the Native SQL Server Connector, some features such as Drag and Drop, ActiveX or .NET may not work.
To restore a correct operating mode, the following code lines should be added into the initialization code of project:
LoadDLL("ole32")
API("ole32", "CoInitializeEx", 0, 2)
Versions 16 and later

Special case: SQL Azure

SQL Azure requires the presence of a "clustered index" in the files.
  • If the data files are created by HCreation, the Native Connector automatically creates the "clustered index" if the description of the data file contains an automatic identifier.
  • If you create the data files with SQL queries (or to add a "clustered index" to an existing data file), see the documentation of SQL Azure to find out the syntax to use.
New in version 16

Special case: SQL Azure

SQL Azure requires the presence of a "clustered index" in the files.
  • If the data files are created by HCreation, the Native Connector automatically creates the "clustered index" if the description of the data file contains an automatic identifier.
  • If you create the data files with SQL queries (or to add a "clustered index" to an existing data file), see the documentation of SQL Azure to find out the syntax to use.

Special case: SQL Azure

SQL Azure requires the presence of a "clustered index" in the files.
  • If the data files are created by HCreation, the Native Connector automatically creates the "clustered index" if the description of the data file contains an automatic identifier.
  • If you create the data files with SQL queries (or to add a "clustered index" to an existing data file), see the documentation of SQL Azure to find out the syntax to use.
Versions 21 and later

Managing calculated items

Calculated items can be used in the data files.
The management of calculated items is available in SQL Server 2005 (or later) with a Native SQL Server Connector via OLE DB or ODBC.
New in version 21

Managing calculated items

Calculated items can be used in the data files.
The management of calculated items is available in SQL Server 2005 (or later) with a Native SQL Server Connector via OLE DB or ODBC.

Managing calculated items

Calculated items can be used in the data files.
The management of calculated items is available in SQL Server 2005 (or later) with a Native SQL Server Connector via OLE DB or ODBC.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment