PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Table of correspondence between the different types of databases, their sources and their databases
  • Failure or success of connection
  • Connection to a HFSQL analysis
  • ODBC and OLE DB: Nesting connections
  • Connection to a database by ODBC
  • Native MySQL, MariaDB and PostgreSQL Accesses
  • Connection to an ISAM database via ACCESS
  • Using a connection with NT authentication
  • Native Oracle access: managing the external authentication
  • SQL query (HExecuteSQLQuery or queries created in the query editor)
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
Connects the current application to a database that will be interrogated by SQL by using a Webservice proxy (SOAP)
Note: This function requires the setup of a Webservice for accessing the databases. See Accessing the databases via a Webservice for more details.
Versions 21 and later
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
New in version 21
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Universal Windows 10 App This function is now available in Universal Windows 10 App mode.
Example
ConnectionNum is int

ConnectionNum = SQLConnectWS("http://MyServer/WDSOAPDB_WEB/", ...
"MS Access 97 Database", "", "", "", "ODBC")
IF ConnectionNum <> 0 THEN
// The connection was successful
 ...
ELSE
// The connection failed: displaying an error message
SQLInfo()
Error("The connection to the data source " + SourceName + ...
" failed." + CR + "Error code: " + ...
SQL.Error + CR + SQL.MesError)
END
// In any case (connection OK or not)
SQLDisconnect()
Syntax
<Result> = SQLConnectWS(<Server of Webservice> , <Source> , <User> , <Password> [, <Database Name> [, <Database Type> [, <OLE DB Provider> [, <Optional Information>]]]])
<Result>: Integer
  • Connection identifier: this identifier is used by SQLChangeConnection.
  • 0 if an error occurred. To find out the error details, use SQLInfo.
<Server of Webservice>: Character string (with quotes)
URL for accessing the server where the Webservice for accessing the external databases was installed. This URL was specified in the wizard for installing the Webservice. See Accessing the databases via a Webservice for more details.
<Source>: Character string (with quotes)
Name of data source (alse called Data Source Name). If the data source contains several "Databases", you must specify the name of the "Database" used (<Database Name> parameter). See remarks for more details.
Native Accesses MySQL: This parameter corresponds to the name or IP address of the computer containing the database. For example, "Apollon".
Native Accesses MySQL and MariaDB: This parameter corresponds to the name or IP address of the computer containing the database. For example, "Apollon".
LinuxUniversal Windows 10 App The source can be a HFSQL Classic or HFSQL Client/Server database.
<User>: Character string (with quotes)
User name. This name is optional for some data sources: in this case, use an empty string ("") for this parameter.
<Password>: Character string
Password corresponding to the specified user. This password is optional for some data sources: in this case, use an empty string ("") for this parameter.
<Database Name>: Optional character string
Name of the database to use. See remarks for more details.
  • If this parameter is specified, a dialog box specific to the driver is displayed during the connection. This dialog box may not be displayed according to the driver used.
  • If this parameter is not specified, no dialog box is displayed.
Native Accesses MySQL: With Native MySQL Access, the database name is mandatory.
Native Accesses MySQL and MariaDB: With Native MariaDB Access, the database name is mandatory.
<Database Type>: Optional character string
Type of database accessed. The types of databases installed on the current computer are returned by SQLListSource. See the notes for more details.
<OLE DB Provider>: Optional character string or constant
Name of OLE DB provider used. The most common ones are as follows:
"SQLOLEDB"SQLSERVER
"MSDASQL"ODBC
"Microsoft.Jet.OLEDB.3.51"Access
"Microsoft.Jet.OLEDB.4.0"Access
"MSDAORA"Oracle (Microsoft)
"OraOLEDB.Oracle"Oracle
or one of the following constants:
hODBCOLE DB provider for ODBC. Allows you to access an ODBC source declared in the ODBC data sources of Windows
hOledbAccess97OLE DB provider for Access 97
hOledbAccess2007OLE DB provider for Access 2007
hOledbAccess2000OLE DB provider for Access 2000
hOledbDBase5OLE DB provider for dBase 5
hOledbExcel2007OLE DB provider for Excel 2007
hOledbExcel2000OLE DB provider for Excel 2000
hOledbExcel97OLE DB provider for Excel 97
hOledbLotus4OLE DB provider for Lotus 4
hOledbOracleOLE DB provider for Oracle
hOledbSQLServerOLE DB provider for SQL Server
Caution: To use an OLE DB connection, you must:
  • install MDAC version 2.6 or later (setup performed by WINDEV or WEBDEV when installing the application)
  • install the OLE DB provider corresponding to the database used.
<Optional Information>: Optional character string (not to be used with HFSQL or direct ODBC)
Used to specify the optional information. You can for example specify "Trusted_Connection=YES" in order to use a connection with authentication via the NT login. If several optional information must be specified, they must be grouped in a single character string and they must be separated by the ";" character.
OLE DBNative Accesses The keywords recognized by OLE DB and the native accesses are presented in the page named Optional connection information.
Remarks
WINDEVWEBDEV - Server codeReports and QueriesAjaxUser code (UMC)HFSQLHFSQL Client/ServerHyper File 5.5OLE DBODBCNative Accesses

Table of correspondence between the different types of databases, their sources and their databases

Database TypeSourceDatabase Name
ACCESSName of Access file"" (empty string)
AS400Native AS/400 access (optional module)
DB2Native DB2 access (optional module)
Source defined in ODBC Administrator
"" (empty string) or Database
HYPER FILEHYPER FILE
Versions 21 and later
HFSQL
New in version 21
HFSQL
HFSQL
Database name"" (empty string)
INFORMIXNative Informix Access (optional module)
JDBCURL for connecting to the database. This URL is specific to each driver.The database must be specified in the connection URL. This URL is specific to each JDBC driver.
Versions 21 and later
HIVE
New in version 21
HIVE
HIVE
URL for connecting to the Hive server.Database
MySQLNative MySQL Access (optional module)
Database name
Database
Versions 20 and later
MariaDB
New in version 20
MariaDB
MariaDB
Native MariaDB Access (optional module)
Database name
Database
POSTGRESQLNative PostgreSQL Access (optional module)
Database name
Database
ODBCSource defined in ODBC Administrator"" (empty string) or Database
OLEDBName of source"" (empty string)
ORACLENative Oracle Access (optional module)
Name of the alias defined in SQL NET Easy configuration and in WDORAINS
"" (empty string)
PROGRESSNative Progress Access (optional module)
Source defined in ODBC Administrator
"" (empty string) or Database
Versions 16 and later
SQL AZURE
New in version 16
SQL AZURE
SQL AZURE
Native SQL Azure Access (optional module supplied with the Native SQL Server Access)
Server name.
If the name of the server is such as: ServerName.database.windows.net, the login must have the following format: login@ServerName
Database
SQL SERVERNative SQL Server Access (optional module)
Server name
"" (empty string)
SYBASENative SYBASE Access (optional module)
Name of server or its alias
"" (empty string)
xBaseNative xBase Access (supplied with the product)
Versions 16 and later
WEBDEV - Browser code "Web SQL database"
New in version 16
WEBDEV - Browser code "Web SQL database"
WEBDEV - Browser code "Web SQL database"
Database available via the browser
(available in Chrome and Safari only)
"" (empty string)
"" (empty string)
LinuxUniversal Windows 10 App The following types of databases are supported: HYPER FILE.
WINDEVWEBDEV - Server codeReports and QueriesAjaxUser code (UMC)HFSQLHFSQL Client/ServerHyper File 5.5OLE DBODBCNative Accesses

Failure or success of connection

If the connection is successful, the connection identifier can be used to change the connection (SQLChangeConnection).
If the connection fails, the SQL.Error and SQL.MesError variables are not initialized. For more details about the connection failure, use SQLInfo.
In any case (failure or success), the connection must be closed (SQLDisconnect).
WINDEVWEBDEV - Server codeReports and QueriesiPhone/iPadUniversal Windows 10 AppAjaxUser code (UMC)HFSQLHFSQL Client/ServerHyper File 5.5

Connection to a HFSQL analysis

For most of the platforms, the access to the HFSQL data (Classic or Client/Server) is available in native mode. There is no need to access the databases via a Webservice proxy (SOAP). To access a HFSQL Client/Server database, all you have to do is use HOpenConnection.
To connect to a HFSQL analysis via a Webservice proxy, use the following syntax:
SQLConnectWS(<Server of Webservice>, ...
<"<Drive>:<Full Analysis WDD Path>", "", "<Analysis Password>")
For example:
// URL of the server that owns the Webservice
sURLWebserviceServer is string = "http://ServerURL"
// WDD of analysis on the server.
// The path is given in relation to the data directory of the Webservice.
sPathAnalysisWDDOnServer is string = ".\" + ProjectInfo(piAnalysis) + ".wdd"
// Password
sWDDPassword is string
// Connection to the HFSQL database according to what is specified in the analysis
IF NOT SQLConnectWS(sURLWebserviceServer, sPathAnalysisWDDOnServer, "", ...
sWDDPassword) THEN
// Connection failure
SQLInfo()
Error(SQL.MesError)
RETURN
END

// Connection OK
// Rest of the code with SQLExec, etc.
Notes:
  • After the connection to a HFSQL analysis, the SQL.Connection variable returns -1.
  • The HFSQL data files will be sought on the server in the current directory of the Webservice programs or in the directory described in the analysis. No path can be specified by programming.
  • If a password was specified for the analysis, this password must be indicated in the third parameter of SQLConnectWS.
  • To handle the HFSQL Client/Server data files, the connection described in the analysis must contain all the necessary information (name or IP Address of the server, port, database, ...): this information cannot be specified by programming.
WINDEVWEBDEV - Server codeReports and QueriesiPhone/iPadAjaxUser code (UMC)OLE DBODBC

ODBC and OLE DB: Nesting connections

For ODBC and OLE DB, several calls to SQLConnectWS can be nested (caution: this is not possible with the HFSQL databases).
The last opened connection is the current connection. SQLChangeConnection is used to modify the current connection.
SQLDisconnect disconnects the current connection.
WINDEVWEBDEV - Server codeReports and QueriesiPhone/iPadAjaxUser code (UMC)ODBC

Connection to a database by ODBC

To connect to a database by ODBC, the following operations must be performed:
  1. Configuring the ODBC data source in the ODBC administrator (on the development computer or on the deployment computer). The data source must be a "system" data source.
  2. Using SQLConnectWS with the "ODBC" parameter.
Note: you have the ability to use an OLE DB provider on ODBC. MDAC must be installed (on the development computer and on the deployment computer). The following syntax must be used:
<Result> = SQLConnectWS(<Server of Webservice>, <Source>, <User>, ...
<Password>, <Database Name>, "OLE DB", hODBC)
Note: The SQL.ODBCHandle variable is used to find out the handle of the ODBC connection for the other SQL functions on ODBC. This variable is filled during the last use of SQLConnectWS. The SQL.HandleODBC variable is set to -1 for the other connections.
WINDEVWEBDEV - Server codeiPhone/iPadAjaxUser code (UMC)Native Accesses

Native MySQL, MariaDB and PostgreSQL Accesses

To open a connection to a MySQL, MariaDB or PostgreSQL database via the native access, the following elements must be passed in parameter to SQLConnectWS:
  • the type of the database used, MySQL, MariaDB or POSTGRESQL.
  • the name of the database: it corresponds to the name given by the administrator of the MySQL/MariaDB/PostgreSQL database.
Note: The name of the MySQL or PostgreSQL data source can be replaced by the name or the IP address of the computer where the database is available. In any case, the name of the "Database" must be specified.
// Connection to a MySQL database
ConnectionNum = SQLConnectWS("http://ServerURL", "MySQLDatabase", ...
"", "", "", "MySQL")
// or
// ConnectionNum = SQLConnect("MySQLDatabase", "User", ...
// "Password", "MyDatabase", "MySQL")

// Connection to a remote MySQL database
ConnectionNum = SQLConnectWS("http://ServerURL", "192.168.1.51", ...
"User", "Password", "test", "MySQL")
Versions 16 and later
Note: The native MariaDB access is available from version 20.
New in version 16
Note: The native MariaDB access is available from version 20.
Note: The native MariaDB access is available from version 20.
WINDEVWEBDEV - Server codeReports and QueriesAjaxUser code (UMC)Native Accesses

Connection to an ISAM database via ACCESS

The following syntax is used to connect to an ISAM database:
SQLConnectWS(<Server of Webservice>, <Database Path>, ...
<User>, <Password>, <Database Type>, "ACCESS")
<Database Path>Path or full name (depending on the case) of the database accessed
<User>User name. It is optional for some databases.
<Password>Password for this user. It is optional for some databases.
<Database Type>Type of the database to which you are connected (therefore, the corresponding ISAM driver must have been installed).
Type of database<Database Type><Database Path>
dBASE III"dBASE III"drive:\directory
dBASE IV"dBASE IV"drive:\directory
dBASE 5"dBASE 5.0"drive:\directory
Paradox 3.x"Paradox 3.x"drive:\directory
Paradox 4.x"Paradox 4.x"drive:\directory
Paradox 5.x"Paradox 5.x"drive:\directory
FoxPro 2.0"FoxPro 2.0"drive:\directory
FoxPro 2.5"FoxPro 2.5"drive:\directory
FoxPro 2.6"FoxPro 2.6"drive:\directory
Excel 3.0"Excel 3.0"Drive:\directory\file.xls
Excel 4.0"Excel 4.0"Drive:\directory\file.xls
Excel 5.0 or Excel 95"Excel 5.0"Drive:\directory\file.xls
Excel 97"Excel 8.0"Drive:\directory\file.xls
HTML Import"HTML Import"Drive:\directory\filename
HTML Export"HTML Export"drive:\directory
Text"Text"drive:\directory
Notes:
  • In order for the requested connection to be established, the corresponding ISAM driver must have have installed. The setup program of MS OFFICE 97 proposes several ISAM drivers.
  • The ACCESS and ISAM databases are accessible in 32-bit mode only.
  • The WLanguage WDBinaryMemo keyword, used to add or modify a binary memo via an SQL query, is not supported by the ACCESS driver.
WINDEVWEBDEV - Server codeReports and QueriesAjaxUser code (UMC)OLE DB

Using a connection with NT authentication

The following syntax allows you to establish a connection with NT authentication:
SQLConnectWS(<Server of Webservice>, <MaDatabase>, Null, Null, Null, ...
"OLEDB", <OLE DB Provider>, "Trusted_Connection=YES")
Versions 18 and later
WINDEVWEBDEV - Server codeNative Accesses

Native Oracle access: managing the external authentication

To connect via an external authentication, the following connection parameters must be used:
  • <User> = / (slash)
  • <Password> = "" (empty string)
Note: The external authentication consists in using the name of Windows user and his password to connect to the database. The external authentication requires a setting of the server. See the documentation about Oracle to find out how to authorize the external authentications on the server.
New in version 18
WINDEVWEBDEV - Server codeNative Accesses

Native Oracle access: managing the external authentication

To connect via an external authentication, the following connection parameters must be used:
  • <User> = / (slash)
  • <Password> = "" (empty string)
Note: The external authentication consists in using the name of Windows user and his password to connect to the database. The external authentication requires a setting of the server. See the documentation about Oracle to find out how to authorize the external authentications on the server.
WINDEVWEBDEV - Server codeNative Accesses

Native Oracle access: managing the external authentication

To connect via an external authentication, the following connection parameters must be used:
  • <User> = / (slash)
  • <Password> = "" (empty string)
Note: The external authentication consists in using the name of Windows user and his password to connect to the database. The external authentication requires a setting of the server. See the documentation about Oracle to find out how to authorize the external authentications on the server.
WINDEVWEBDEV - Server codeAjaxUser code (UMC)HFSQLHFSQL Client/ServerHyper File 5.5OLE DBODBCNative Accesses

SQL query (HExecuteSQLQuery or queries created in the query editor)

When using the SQL DELETE, INSERT or UPDATE statements, no integrity check and no duplicate check are performed on a HFSQL database. This feature is not available in this version.
Solution: Use the HFSQL functions (HDelete, HAdd or HModify) on your data files. The integrity check and the duplicate check will be automatically performed.
Components
WINDEVWEBDEV - Server codeReports and Queries wd230hf.dll
Linux wd230hf.so
Android wd230android.jar
Minimum required version
  • Version 19
This page is also available for…
Comments
Click [Add] to post a comment