ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

Help / Native Connectors/Native Accesses / Native SQLite Connector
  • Overview
  • Importing the structure of files
  • The import steps
  • Taking into account the evolutions of the SQLite database
  • Programming
  • 1. Opening the connection
  • 2. Running queries
  • 3. Retrieving the result
  • 4. Closing the connection
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
To use an SQLite database with Native Connector (also called Native Access), the structure of SQLite tables must be imported into the data model editor.
Differences compared to SQL programming: The queries are not required to handle the SQLite data. Indeed, the HFSQL functions can be directly used to read data, perform searches, implement filters, ... However, the structure of SQLite files must be imported into the data model editor.
Importing the structure of files

The import steps

To perform this import:
  1. Start the data model editor: click Load project analysis in the quick access buttons.
  2. On the "Analysis" tab, in the "Creation" group, expand "Import" and select "Import file/table descriptions...".
  3. The wizard starts. A connection to the SQLite database is automatically established and associated with the files imported into the analysis. This connection will have to be used to handle the SQLite data file through programming.
In the different steps of the wizard, choose the following options:
  • Type of database: SQLite.
  • Characteristics of the connection: Data server, User and password, database.
  • The application will access the data in the current format.
  • When the connection is established, all you have to do is select the tables that will be imported into the WINDEV or WEBDEV analysis. These tables can be handled through programming with the HFSQL functions of WLanguage. These tables will be displayed in blue in the data model editor.

Taking into account the evolutions of the SQLite database

To take into account the evolutions of the tables imported into the data model editor, go to the "Analysis" tab, "Analysis" group, expand "Synchronization" and select "Update analysis from external databases".
A wizard starts, allowing you to:
  • analyze the differences for the imported tables.
  • analyze the differences for all the SQLite tables.
Programming

1. Opening the connection

To establish the connection to the SQLite database, use HOpenConnection and specify the name of the connection to open. The connection name was defined when importing the structure of files into the analysis.
To modify some parameters of this connection (username or password for example), call HConnect.
Remark: If you try to read the file directly (HReadFirst, ...), the connection associated with the file description in the analysis will be automatically opened.

2. Running queries

HExecuteQuery and HExecuteSQLQuery are used to run queries on the current database.
  • HExecuteQuery: is used to run a preset query with the query editor.
  • HExecuteSQLQuery: is used to execute a query by specifying the SQL code of the query and the name that will be assigned to this SQL code.
// Initialize the "Customer_84" query
HExecuteQuery(CUSTOMER_84, "SQLiteDatabase", hQueryWithoutCorrection)
HExecuteSQLQuery(CustomerQry, "SQLiteDatabase", hQueryWithoutCorrection, "SELECT NAME FROM CUSTOMER")

3. Retrieving the result

The result is browsed by the standard read functions: HReadFirst, HReadNext, HReadSeek, ...
The records cannot be locked by the lock options of these functions.

4. Closing the connection

HCloseConnection is used to close the connection to the database once all the necessary queries have been run.
Minimum version required
  • Version 16
This page is also available for…
Comments
Click [Add] to post a comment

Last update: 05/26/2022

Send a report | Local help