[Solved) SQLite3.dll not found
lazarus / 16-Databases

----------------------------------------------------------------------
folkeu08 · 2020-10-04 08:53

Hi,
I am using a SQLite3 database.
Lazarus tells me that I cannot find SQLite3.dll.
i am under 64 bit W10 and unzipped the original binaries (sqlite3.dll
and .def) into "System32" and "SysWOW64" and also into the application
directory.
Is there like MySQL need an MS Visual C ++ 2013 Redistributable x32
and x64 to install?
In the properties of the connection component, I have set it to
active.
The other forums all indicate that it is enough to copy these dlls in
the windows syteme directories but in my case it takes a supplement.
Thank you

----------------------------------------------------------------------
wp · 2020-10-04 10:05

You seem to have a 64-bit windows running, and you must be careful,
since Lazarus can create both 32bit and 64-bit applications..
According to the sqlite3 download page there are pre-compiled versions
for 32bit and 64 bit applications. You must copy the 64-bit dll into
c:\windows\system32 and the 32-bit dll into SysWOS64 (what a nonsense
in naming! - see also https://www.howtogeek.com/326509/whats-the-
difference-between-the-system32-and-syswow64-folders-in-windows/). I
think that it is not necessary to copy the dll into the program
directory under this configuration. If you do, again you must take
care of the bitness of the dll: When you application is 64bit you need
the 64bit dll, and when your application is 32bit you need the 32bit
dll.

----------------------------------------------------------------------
PascalDragon · 2020-10-04 11:22

Quote from: wp on October 04, 2020, 12:05:08 pmYou must copy the
64-bit dll into c:\windows\system32 and the 32-bit dll into SysWOS64
(what a nonsense in naming! - see also
https://www.howtogeek.com/326509/whats-the-difference-between-the-
system32-and-syswow64-folders-in-windows/).
Why is it a nonsense in naming (it's SysWOW64 btw.)? It stands for
“System Windows on Windows 64” and fits into the 8 characters limit
(Windows XP had a 64-bit variant as well and could still be installed
on FAT!).

----------------------------------------------------------------------
folkeu08 · 2020-10-04 11:37

@WP
Very thanks.
You are right, the 64 bits DLL must be in System32 and 32 bits in
sysWow64.
Now, it's good. I did the opposite.
Thanks

----------------------------------------------------------------------
wp · 2020-10-04 11:37

Quote from: PascalDragon on October 04, 2020, 01:22:09 pmQuote from:
wp on October 04, 2020, 12:05:08 pmYou must copy the 64-bit dll into
c:\windows\system32 and the 32-bit dll into SysWOS64 (what a nonsense
in naming! - see also https://www.howtogeek.com/326509/whats-the-
difference-between-the-system32-and-syswow64-folders-in-windows/).
Why is it a nonsense in naming (it's SysWOW64 btw.)?
Because the 64-bit dlls go into System32, and the 32-bit dlls go into
SysWOW64. Every "normal" person would expect the 32-bit dlls to be in
System32 and the 64-bit dlls to be in a directory named with a "64"
appendix. Why didn't they introduce a System64 folder for the 64-bit
dlls and left the 32 bit in System32? 64bit introduced many changes
and application writers could have fixed their hard-coded System32
calls along the way.