WINDEV and WEBDEV propose an optional Native Connector (also called Native Access) to SQL Server. This Native Connector supports the versions 7, 2000, 2005, 2008, 2012 and 2014 as well as the Express versions of SQL Server. This Native Connector allows you to access a SQL SERVER database from a WLanguage program without using any external driver.

SQLnCli is the client layer supplied from SQL Server 2005.This access method should be used in the new developments.

This method allows you to use the different client layers proposed by Microsoft:

Versions 18 and laterSQLnCli 11 (recommended): it is the client layer corresponding to SQL Server 2012 and later. Caution: the SQLnCli 11 client layer does not allow you to connect to SQL Server 2000 servers and earlier.

New in version 18SQLnCli 11 (recommended): it is the client layer corresponding to SQL Server 2012 and later. Caution: the SQLnCli 11 client layer does not allow you to connect to SQL Server 2000 servers and earlier.

SQLnCli 11 (recommended): it is the client layer corresponding to SQL Server 2012 and later. Caution: the SQLnCli 11 client layer does not allow you to connect to SQL Server 2000 servers and earlier.

SQLnCli 10: it is the client layer corresponding to SQL Server 2008. It is required to exploit the new features of version 17 (new TIME and DATE types for example).

SQLnCli: this client layer corresponds to SQL Server 2005. It is more efficient than SQLOLEDB must it must be installed on the user computers.

SQLOLEDB: this client layer was supplied from SQL Server 2000. It is found in the Microsoft operating systems from Windows XP.

The Native SQL Server Connector is used to access the client layer SQLnCli:

via an access by OLE DB (recommended).

Versions 19 and latervia an access by ODBC.

New in version 19via an access by ODBC.

via an access by ODBC.

Notes:

Versions 16 and later

The Native SQL Server Connector via SQLnCli is available in 32 bits and in 64 bits.

Versions 18 and laterCaution: if the client layer 2012 is installed, you will not be able to connect to SQLServer 2000 servers and earlier. The extended information "WD CLIENT VERSION" allows you to force the use of a specific client layer.

New in version 18Caution: if the client layer 2012 is installed, you will not be able to connect to SQLServer 2000 servers and earlier. The extended information "WD CLIENT VERSION" allows you to force the use of a specific client layer.

Caution: if the client layer 2012 is installed, you will not be able to connect to SQLServer 2000 servers and earlier. The extended information "WD CLIENT VERSION" allows you to force the use of a specific client layer.

DB-Library is supplied with the versions of SQL Server earlier than 2005.This method is kept for backward compatibility and its use is not recommended.

In 32 bits:

The wdxxxsqlserver.dll DLL is required for this use mode of Native Connector via OLE DB.

Versions 19 and laterThe wdxxxsqlserver2.dll DLL is required for this use mode of Native Connector via OBDC.

New in version 19The wdxxxsqlserver2.dll DLL is required for this use mode of Native Connector via OBDC.

The wdxxxsqlserver2.dll DLL is required for this use mode of Native Connector via OBDC.

In 64 bits:

Versions 16 and laterThe wdxxxsqlserver64.dll DLL is required for this use mode of Native Connector via OLE DB.

New in version 16The wdxxxsqlserver64.dll DLL is required for this use mode of Native Connector via OLE DB.

The wdxxxsqlserver64.dll DLL is required for this use mode of Native Connector via OLE DB.

Versions 19 and laterThe wdxxxsqlserver2_64.dll DLL is required for this use mode of Native Connector via OBDC.

New in version 19The wdxxxsqlserver2_64.dll DLL is required for this use mode of Native Connector via OBDC.

The wdxxxsqlserver2_64.dll DLL is required for this use mode of Native Connector via OBDC.

We advise you to download and install the last version of the SQLnCLI layer (sqlncli.msi file on the Microsoft site).

The wdxxxsqs.dll DLL is required for this use mode of Native Connector.

The NTWDBLIB.DLL DLL, installed by "SQL Server Client Utilities", is also required.

Versions 16 and laterThe Native SQL Server Connector via SQLnCli now supports the access to SQL Azure databases.
This feature requires an update of WINDEV and WEBDEV (version later than 160047).

New in version 16The Native SQL Server Connector via SQLnCli now supports the access to SQL Azure databases.
This feature requires an update of WINDEV and WEBDEV (version later than 160047).

The Native SQL Server Connector via SQLnCli now supports the access to SQL Azure databases.
This feature requires an update of WINDEV and WEBDEV (version later than 160047).

Note: This documentation is common to both use modes of Native Connector. The differences in operations or in behavior are indicated when necessary.

Benefits for using Native SQL Server Connector:

The HReadxxx functions (HReadNext, HModify, ...) can be used on the SQL Server databases. Which means that a SQL Server database and a HFSQL database are handled by the same commands. Porting an existing application to external databases is simplified.

The RAD allows you to generate the code with the Hxxx functions (HReadNext, ...) or with the SQLxxx functions.

WDMap (the data viewer) can be used with your SQL Server databases.

Supporting all the version of SQL Server databases (from 7).

The performances are greater than the ones of an access by ODBC for example.

The use of this Native Connector is highly recommended when developing Client/Server applications (that access SQL Server databases) with WINDEV or WEBDEV. Feel free to contact us for any additional information.

Note: Contact PC SOFT sales department if you do not own Native SQL Server Connector.

New features of version 21

Versions 21 and laterThe main new features of version 21 are:

Managing the default values. The default values of items are now supported for the different Native SQL Server Connectors (SQL Server via SQLnCli by OLE DB or ODBC and SQL Server via DB-Library). 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.

Managing the calculated items. You now have the ability to use calculated items in the data files. The management of calculated items is available with SQL Server 2005 (or later) via a Native SQL Server Connector via SQLnCli by OLEDB or ODBC. This feature is not available for Native SQL Server Connector via DB-Library.

New in version 21The main new features of version 21 are:

Managing the default values. The default values of items are now supported for the different Native SQL Server Connectors (SQL Server via SQLnCli by OLE DB or ODBC and SQL Server via DB-Library). 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.

Managing the calculated items. You now have the ability to use calculated items in the data files. The management of calculated items is available with SQL Server 2005 (or later) via a Native SQL Server Connector via SQLnCli by OLEDB or ODBC. This feature is not available for Native SQL Server Connector via DB-Library.

The main new features of version 21 are:

Managing the default values. The default values of items are now supported for the different Native SQL Server Connectors (SQL Server via SQLnCli by OLE DB or ODBC and SQL Server via DB-Library). 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.

Managing the calculated items. You now have the ability to use calculated items in the data files. The management of calculated items is available with SQL Server 2005 (or later) via a Native SQL Server Connector via SQLnCli by OLEDB or ODBC. This feature is not available for Native SQL Server Connector via DB-Library.

configure the connection in the data model editor by using HDescribeConnection or in WDSQSINS (optional step). WDSQSINS is used to complete the parameters defined in the data model editor or with HDescribeConnection.