Jump to content

FT_Uhu

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. I resolved the problem. It appears that in some another unit in uses was FireDAC.Phys.SQLiteWrapper.Stat. And this cause to the error. When I remove everywhere (designer on form if you create connection or TFDQuery also will put this unit in uses automatic, so I moved creating everything in code) all begin working fine.
  2. Hi all, I am working with Delphi FireDAC and SQLite, and I recently ran into an issue after upgrading to RAD Studio 12.3. In previous versions (prior to RAD Studio 12.0), I was using SQLite 3.31.1 with FireDAC encryption (FDE), which worked well for my use case. However, as RAD Studio 12.0 introduced support for SQLite 3.42, I noticed some changes that impacted my project. To summarize, RAD Studio 12.0 added support for SQLite 3.42 while still maintaining compatibility with SQLite 3.31.1, and it was possible to use FireDAC encryption (FDE) with SQLite 3.31.1. Starting from SQLite 3.42, SQLite dropped the mechanism that FireDAC uses for encryption, so the encryption feature is no longer available with SQLite 3.42 or newer unless we use the paid SQLite EE with native encryption support. For those still wanting to use FireDAC encryption with SQLite, here are the available options: Use the latest SQLite version without FireDAC encryption. Use SQLite EE (Enterprise Edition), which has native encryption support. Stick with SQLite 3.31.1 or earlier versions if you want to continue using FireDAC encryption (FDE). I have been continuing with SQLite 3.31.1, and FireDAC’s encryption worked fine with FireDAC.Phys.SQLiteWrapper.FDEStat in uses in version 12.2. However, after upgrading to RAD Studio 12.3, I now encounter an Access Violation when using this. Has anyone else faced this issue? If so, does anyone have any advice on how to fix or work around this problem in RAD Studio 12.3? Any insights or solutions would be greatly appreciated! Thanks in advance
×