SQLite Database Encryption Issue

SQLite Database Encryption Issue

This article is for dotConnect for SQLite.

When working with SQLite databases in applications built with dotConnect for SQLite, built-in encryption may fail to work. This usually happens either because of edition limitations or because the wrong version of the SQLite library is being used. The instructions below describe the requirements and configuration needed for encryption to function correctly.

Edition requirement

Built-in encryption support is available only in the Professional Edition of dotConnect for SQLite. If you are using another edition, encryption will not be available.

Correct SQLite library

The application must use the sqlite3.dll supplied with dotConnect for SQLite rather than the standard SQLite library.

To configure this:

1. In the current directory of your application, create two subfolders:
  1. x86
  2. x64
2. Copy the appropriate sqlite3.dll into these folders:
  1. x86: C:\Program Files (x86)\Devart\dotConnect\SQLite\sqlite3.dll
  2. x64: C:\Program Files (x86)\Devart\dotConnect\SQLite\x64\sqlite3.dll
This ensures that the correct library is used depending on the bitness of the application.

    • Related Articles

    • Excel Add-ins. Slow Data Extraction (Database Providers)

      This article is for Excel Add-ins (Databases). Navigation: Supported Data Sources → Supported databases: Data loading into Excel may work noticeably slower compared to executing the same query in other tools. Performance can be improved by adjusting ...

    • What SQL Syntax Can Be Used with Devart ODBC Drivers?

      Devart ODBC Drivers internally rely on the SQLite engine to execute SQL queries. This means that all SQL statements executed through the driver must conform to the SQLite SQL dialect. The SQLite engine supports a wide range of SQL features including: ...

    • How to Expedite Error Report Resolution

      In addition to the standard procedure for submitting an Error Report, the following steps can significantly help us resolve the issue more quickly and efficiently. While the information provided in the original report is valuable, these additional ...

    • Timestamps Not in Expected Timezone in dbForge Studio for Oracle

      If you're encountering timestamps that don't match your system's timezone in dbForge Studio for Oracle, this can typically be resolved with a quick configuration update. This issue may arise due to default formatting settings or discrepancies in how ...

    • Resolving ORA-12705 Error

      The ORA-12705 error, "Invalid or unknown NLS parameter value specified," typically arises when the NLS_LANG environment variable on your deployment server is configured with an invalid language, territory, or character set. This mismatch between the ...