Devart Forums

Hi, I'm using Unidac version 6.3.12 for Builder c++ 6.0 on Windows 10
With Unidac I connect my software to SQLite.
This is a piece of my code

DMod->ConnectionGare->ConnectString = "Provider Name=SQLite;Database=" + fileNameGara + ";Use Unicode=True;Login Prompt=False";
DMod->ConnectionGare->SpecificOptions->Clear();
DMod->ConnectionGare->SpecificOptions->Add("BusyTimeout=500000");
DMod->ConnectionGare->SpecificOptions->Add("ReadUncommitted=True");
DMod->ConnectionGare->SpecificOptions->Add("Direct=True");
DMod->ConnectionGare->SpecificOptions->Add("UseUnicode=True");
DMod->ConnectionGare->SpecificOptions->Add("EnableSharedCache=True");

TUniSQL *cmd = CreateNewCommand(DMod->ConnectionGare);
cmd->SQL->Text = "PRAGMA foreign_keys = ON;";
cmd->Execute();
cmd->SQL->Text = "PRAGMA journal_mode = WAL;";
cmd->Execute();
cmd->SQL->Text = "PRAGMA synchronous = NORMAL;";
cmd->Execute();

If I do some operations I have windows blue screen.
Could unidac cause windows blue screen in a strange case?

In the past I used TADO connection with access database and I never had windows blue screen

UniDAC does not support the WAL mode of the Journal_Mode parameter when working with SQLite. Try using some other Journal_Mode value ( http://www.sqlite.org/pragma.html#pragma_journal_mode ). If the described error occurs even after changing the value of Journal_Mode, try reproducing the issue with the latest version of UniDAC 7.2.5 (18-Jan-2018) and let us know about the results.

Hi, thank you for you answer.
I changed my code so

cmd->SQL->Text = "PRAGMA journal_mode = DELETE;";
cmd->Execute();

I tested and it seems be better.
I will do other test.

My license is expired so I can't try with last version

You can test your project using a fully-featured trial version of UniDAC at https://www.devart.com/unidac/download.html
You can renew your existing subscription an existing subscription at our website http://www.devart.com/unidac/ordering.html in the Subscription Renewals section the Renewals & Upgrades tab.