|
|
|
|
|
|
|
|
|
|
Database management in Java WINDEV applications
This document presents the different access modes to databases from a WINDEV Java application. | | | | | Database/Operating system | Windows | Linux | Mac | | HFSQL Client/Server or network | Direct access with the Hxx or SQLxx functions with the following DLLs in the runtime directory:- wd300hf.dll
- wd300jav.dll
- wd300sql.dll
- wd300vm.dll
Depending on the features used, the following libraries may also be required: wd300pnt.dll, wd300trs.dll, wd300uni.dll.These libraries are located in WINDEV's "Programs" subdirectory. | Direct access with the Hxx or SQLxx functions with the following libraries in the runtime directory:- wd300hf.so
- wd300jav.so
- wd300sql.so
- wd300vm.so
Depending on the features used, the following libraries may also be required: wd300pnt.so, wd300trs.so, wd300uni.so.These libraries are available in the "Programs\Framework\Linux" subdirectory of WINDEV. | Direct access with the Hxx or SQLxx functions with the following libraries in the runtime directory:- wd300hf.dylib
- wd300jav.dylib
- wd300sql.dylib
- wd300vm.dylib
These libraries are available in the "Programs\Framework\MacOSX" subdirectory of WINDEV. | Note:- For a direct access to an HFSQL Classic Network database, the data must be found on the local network. The data cannot be found on a Windows share accessible from the Mac.
- For an HFSQL Client/Server database, the data can be found locally or remotely.
| | Native MySQL, SQL Server or SQLite Access | Direct access possible with the Hxxx or SQLxxx functions (no DLL on the user computer) | Direct access possible with Hxxx or SQLxxx functions (without .so on the user's workstation) | Direct access possible with the Hxxx or SQLxxx functions (no .dylib on the user computer) | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Windows | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Linux | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Mac | | Any database that includes a JDBC driver | Direct access possible with the SQLxxx functions only (no DLL on the user computer) | Direct access possible with the SQLxxx functions only (no .so on the user computer) | Direct access possible with the SQLxxx functions only (no .dylib on the user computer) | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Windows | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Linux | Notes:
- The JDBC driver must be included in the archive
- Make sure that the JDBC driver is compatible with Mac |
Some important points regarding the access to data from a Java application in WINDEV: - The execution performed in test mode is not a Java execution but a Windows execution. A different connection must therefore be made if test mode is used or not (for example: InTestMode()=True).
- The RMI and JDBC connections cannot be defined in the analysis. These connections must be programmed (function SQLConnect or function HOpenConnection).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|