PC SOFT

ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Home | Sign in | English EN
  • Overview
  • Use
  • Using Native SQL Server Connector in your WINDEV applications or WEBDEV sites
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Others
Stored procedures
Overview
WINDEV and WEBDEV support an optional Native SQL Server Connector (also called Native SQL Server Access). This Native Connector supports versions 7, 2000, 2005, 2008, 2012, 2014 and 2016 as well as the Express versions of SQL Server. This Native Connector allows you to access an SQL SERVER database from a WLanguage program without using any external driver.
The Native SQL Server Connector offers several modes of use:
SQL Server via OLE DBSQL Server via ODBC
The Native SQL Server Connector is used to access the client layer via OLE DB.
This method allows you to use the different client layers proposed by Microsoft:
  • MSOLEDBSQL (recommended)
  • SQLnCli 11: Client layer corresponding to SQL Server 2012.
  • SQLnCli 10: Client layer corresponding to SQL Server 2008.
  • SQLnCli: Client layer corresponding to SQL Server 2005. It is more powerful than SQLOLEDB but needs to be installed on user computers.
  • SQLOLEDB: Client layer released from SQL Server 2000 onwards. It can be found in Microsoft operating systems from Windows XP.
This method is available in 32-bit and 64-bit Windows.
The Native SQL Server Connector is used to access the client layer via ODBC.
This method allows you to use the different client layers proposed by Microsoft:
  • msodbcsql17 (recommended)
  • msodbcsql13
  • SQLnCli 11
  • SQLnCli 10: Client layer corresponding to SQL Server 2008. From this version, it is possible to use the new TIME and DATE types for example (new features in version 17).
  • SQLnCli: Client layer corresponding to SQL Server 2005. It is more powerful than SQLOLEDB but needs to be installed on user computers.


This method is available in 32-bit and 64-bit Windows, and in 64-bit Linux.
In 32-bit versions, wdxxxsqlserver.dll is required for this mode of use of the Native Connector via OLE DB.
In 64-bit versions, wdxxxsqlserver64.dll is required for this mode of use of the Native Connector via OLE DB.
In 32-bit versions, wdxxxsqlserver2.dll is required for this mode of use of the Native Connector via OBDC.
In 64-bit versions, wdxxxsqlserver2_64.dll is required for this mode of use of the Native Connector via ODBC.

Remarks:
  • The Native SQL Server Connector manages access to SQL Azure databases.
  • This documentation is common to both modes of use of the Native Connector. Different actions or behavior are indicated when necessary.
Here are some of the many advantages of using the Native SQL Server Connector:
  • The HReadxxx functions (HReadNext, HModify, ...) can be used on the SQL Server databases. Which means that an SQL Server database and an 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.
  • Support of SQL Server databases in all versions (from version 7).
  • Better performance compared to an access via ODBC, for example.
  • The Native Connector is used to exploit an important number of features (stored procedures, HPrepareSQLQuery, ...)
  • etc.
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.
Remark: Contact PC SOFT sales department if you do not own Native SQL Server Connector.
Use

Using Native SQL Server Connector in your WINDEV applications or WEBDEV sites

To use SQL Server in native mode, you must:
Remarks:
  • The version of the Native Connector can be chosen via the H.SQLServerMode variable.
  • Don't forget to read the limitations of the Native SQL Server Connector.
  • To deploy sites that use the Native SQL Server Connector, the latter must be installed on the server (WEBDEV application server).
  • Versions 23 and later
    The option "Automatically create the data files if they do not exist" (found in the "Files" tab of project description) is taken into account by Native SQL Server Connector.
    New in version 23
    The option "Automatically create the data files if they do not exist" (found in the "Files" tab of project description) is taken into account by Native SQL Server Connector.
    The option "Automatically create the data files if they do not exist" (found in the "Files" tab of project description) is taken into account by Native SQL Server Connector.
  • Versions 24 and later
    The Msoledbsql driver for SQL Server is supported by the SQL Server Native Connector.
    New in version 24
    The Msoledbsql driver for SQL Server is supported by the SQL Server Native Connector.
    The Msoledbsql driver for SQL Server is supported by the SQL Server Native Connector.
  • Versions 24 and later
    Thread error management: When a call to the SQL Server Native Connector is made from a thread, it is possible to manage errors in a normal way.
    New in version 24
    Thread error management: When a call to the SQL Server Native Connector is made from a thread, it is possible to manage errors in a normal way.
    Thread error management: When a call to the SQL Server Native Connector is made from a thread, it is possible to manage errors in a normal way.
  • Versions 24 and later
    The Native SQL Server Connector supports UUIDs.
    New in version 24
    The Native SQL Server Connector supports UUIDs.
    The Native SQL Server Connector supports UUIDs.
Minimum version required
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment