PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Required configuration
  • Conditions for using Native MySQL Access
  • The necessary files
  • Installing a new version of MySQL
  • Files required to use native MySQL access in Linux
  • Use
  • Using the native MySQL access in your WINDEV applications and WEBDEV sites
  • Optimizing HFSQL functions
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
Overview
WINDEV and WEBDEV 23 propose a module for Native Access to MySQL. This native access allows you to access a MySQL database from a program in WLanguage without using any external driver.
Caution: This version of Native MySQL Access operates with WINDEV and WEBDEV version 23. The Native MYSQL Access is not available for WINDEV Mobile. If you are using WINDEV Mobile, the access to a foreign database (MySQL, Oracle, SQL Server) must be performed via a Webservice supplied with WINDEV Mobile. See the help about SQLConnectWS for more details.
Note: The Native MySQL Access is an optional and free module available for download from the PC SOFT site
Required configuration
WINDEVWEBDEV - Server codeWindowsNative Accesses

Conditions for using Native MySQL Access

  • Client layer of MySQL (LibMySQL.DLL file)
    • 32-bit client layer to use the 32-bit Native MySQL Access (version 3.x to 5.x).
    • Versions 17 and later
      64-bit client layer to use the 64-bit Native MySQL Access (version 5.x).
      New in version 17
      64-bit client layer to use the 64-bit Native MySQL Access (version 5.x).
      64-bit client layer to use the 64-bit Native MySQL Access (version 5.x).
  • The LibMySQL.DLL DLL must be found:
    • On the development computer, in the "Programs" directory of the setup directory of WINDEV or WEBDEV.On the development computer:
      • in the "\Programs\Framework\Win32x86" directory of the setup directory of WINDEV or WEBDEV (32 bits).
      • in the "\Programs\Framework\Win64x86" directory of the setup directory of WINDEV or WEBDEV (64 bits).
    • On the deployment computer, in the executable directory or in the Windows directory. For a deployment on a Web server, the DLL must be found in the directory of the Native Access or in the Windows directory.
WINDEVWEBDEV - Server codeWindowsNative Accesses

The necessary files

The following files are required to use the native MySQL access:
  • The LibMySQL.DLL DLL. This DLL is supplied with MySQL. See the license agreement of MySQL for more details about the distribution conditions of this DLL.
    • 32-bit file to use the 32-bit Native MySQL Access.
    • Versions 17 and later
      64-bit file to use the 64-bit Native MySQL Access.
      New in version 17
      64-bit file to use the 64-bit Native MySQL Access.
      64-bit file to use the 64-bit Native MySQL Access.
    From version 5.5 of libmysql.dll client, the computer that runs the application must install a Visual Studio Redistributable package corresponding to the server version (see the Oracle site for more details).
  • The wdxxxmsql.dll DLL: Required for the 32-bit native access to a MySQL database. This file is supplied with the Native MySQL Access for WINDEV or WEBDEV.
  • Versions 17 and later
    The wdxxxmsql64.dll DLL: Required for the 64-bit native access to a MySQL database. This file is supplied with the Native MySQL Access for WINDEV or WEBDEV.
    New in version 17
    The wdxxxmsql64.dll DLL: Required for the 64-bit native access to a MySQL database. This file is supplied with the Native MySQL Access for WINDEV or WEBDEV.
    The wdxxxmsql64.dll DLL: Required for the 64-bit native access to a MySQL database. This file is supplied with the Native MySQL Access for WINDEV or WEBDEV.
Versions 17 and later
To debug a multi-configuration project in 32-bit and 64-bit configuration:
  • copy the 32-bit libmysql DLL into the EXE sub-folder of 32-bit configuration of project.
  • copy the 64-bit libmysql DLL into the EXE sub-folder of 64-bit configuration of project.
New in version 17
To debug a multi-configuration project in 32-bit and 64-bit configuration:
  • copy the 32-bit libmysql DLL into the EXE sub-folder of 32-bit configuration of project.
  • copy the 64-bit libmysql DLL into the EXE sub-folder of 64-bit configuration of project.
To debug a multi-configuration project in 32-bit and 64-bit configuration:
  • copy the 32-bit libmysql DLL into the EXE sub-folder of 32-bit configuration of project.
  • copy the 64-bit libmysql DLL into the EXE sub-folder of 64-bit configuration of project.
WINDEVWEBDEV - Server codeWindowsNative Accesses

Installing a new version of MySQL

The dialog between native MySQL access and MySQL is using the LIBMYSQL.DLL DLL supplied with MySQL.
The Native Access may no longer operate if the behavior of this DLL is modified (when changing version for example).
An upgraded version that takes these changes into account will be available soon ; meanwhile, all you have to do is use the previous version of LIBMYSQL.DLL. This DLL will operate with the new version of MySQL, while still being compatible with the Native Access.
WINDEVWEBDEV - Server codeLinuxNative Accesses

Files required to use native MySQL access in Linux

To use native MySQL access in Linux, the following operations must be performed:
1. Install the MySQL client layer on the server. Check whether the libmysqlclient.so DLL was copied into /usr/lib.
Note:
  • The 32-bit MySQL client layer must be installed to use the 32-bit native MySQL access.
  • Versions 17 and later
    The 64-bit MySQL client layer must be installed to use the 64-bit native MySQL access.
    New in version 17
    The 64-bit MySQL client layer must be installed to use the 64-bit native MySQL access.
    The 64-bit MySQL client layer must be installed to use the 64-bit native MySQL access. If the copied DLLs are such as libmysqlClient.so.12.0.0, a link must be created on this DLL with the following code line:
ln -s libmysqlclient.so.12.0.0 libmysqlclient.so
2. If you are using a WEBDEV site, copy the following DLLs into the directory of WEBDEV application server:
  • wd230hf.so: HFSQL library
  • wd230msql.so: library of 32-bit native access
  • Versions 17 and later
    wd230msql64.so: library of 64-bit native access
    New in version 17
    wd230msql64.so: library of 64-bit native access
    wd230msql64.so: library of 64-bit native access
  • wd230sql.so: SQL library
3. If you are using a Java application or a Linux batch application, copy the following DLLs into the application directory:
  • wd230hf.so: HFSQL library
  • wd230msql.so: library of 32-bit native access
  • Versions 17 and later
    wd230msql64.so: library of 64-bit native access
    New in version 17
    wd230msql64.so: library of 64-bit native access
    wd230msql64.so: library of 64-bit native access
  • wd230sql.so: SQL library
Use

Using the native MySQL access in your WINDEV applications and WEBDEV sites

To use MySQL in native mode, you must program in the WINDEV application or WEBDEV site:
Notes:
  • Don't forget to read the limitations regarding the use of Native MySQL Access.
  • 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 MySQL 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 MySQL 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 MySQL Connector.
Note: From version 19, HFSQL is the new name of HyperFileSQL.

Optimizing HFSQL functions

  • The "Browsing table" controls based on queries are optimized: the content of the Table control can be sorted by clicking one of its columns.
  • To avoid re-running the same query several times when browsing its result, we advise you to use the hNoRefresh constant (if the data is modified by a single computer for example).
Minimum required version
  • Version 9
This page is also available for…
Comments
Click [Add] to post a comment