Attempt to Install sqlite3laz 0.4 Components crashes Lazarus

[1HuntnMan]

Anyone who might know why this is happening please reply... I've attempted this 3 times. Steps I am following:

Package -> Install/Uninstall Packages -> Scroll down right-column to sqlite3laz 0.4 and select it -> Install selection -> Save and Rebuild IDE.

After compiling I receive missing files and aborts Lazarus. Then if I attempt to launch Lazarus, Laz refuses with the error attached.

It appears Lazarus needs additional files??????

[paweld]

Copy sqlite3.dll library to lazarus folder

[cdbc]

Hi
1) You need to copy 'sqlite3.dll' into the directory where Lazarus itself is
    located. So that it can find it when Lazarus starts.
2) You need to copy 'sqlite3.dll' into the directory where the project you're
    developing is residing and to be safe copy the library with your application
    when you distribute it. *)
*) Every application you develop with SQLite3 as backend, as it is now a
    dependency of your project.

...or
You need to copy 'sqlite3.dll' into the windows system directory, so that it's accessible to all apps on your system. This you also have to make sure on your client's computer, when you distribute it.

As always with libraries (dlls), beware of versions!
Regards Benny

eta: paweld beat me to it... 

[1HuntnMan]

That's what I was thinking last night after I was frustrated, with the install, Laz can't find the SQLite3.dll. I have it in my project directory.
I'm going to copy it to the Lazarus folder/dir and also to the Winders Systerm32 directory. My Windows 11 computer doesn't have anything in the System directory.
Thanks...

[1HuntnMan]

Okay, that fixed it, now have the SQLite3Dataset component! Thanks all!

[Thaddy]

Okay, that fixed it, now have the SQLite3Dataset component! Thanks all!

Except you should not use that and use sqldb with sqlite3 as back-end.
That is because SQLite3Dataset has a bug since over 20 years, is not maintained, and that caused your issue:
- SQLite3Dataset assumes sqlite3 is installed and otherwise simply crashes. That is normal?
- SQLdb with an SQlite3 back-end will recover with a SQLite3 not found.

Frankly I do not understand why it is not removed. (or fixed)
I also do not understand why you use it. Use SQLdb with the SQLite3 back-end.