On Jun 15, 6:29 pm, Salvor Hardin <salvor.pub...@gmail.com> wrote: > It would be great if web2py.exe loads sqlite3.dll from the same > directory as web2py.exe. > > Unfortunately, web2py loads C:\Windows\System32\sqlite3.dll which is > the most unpredictable version of sqlite3.dll on Windows.
Hmmm.... this may have to do with your library load path; I'm not sure what that is for windows, but if it's loading the way you say, I would look at your user environment, for I would guess it is doing the same for your normal python executions (I would have suggested the source distro of web2py, except I expect you will still run into this, because I suspect it has to do with your dynamic library load order for your user instance). Let us know what you find. > I didn't realize this until I tried replacing C:\web2py\sqlite3.dll > with an encryption-enabled version. I confirmed using Process > Explorer to see which sqlite3.dll was loaded by web2py.exe. > > I have 3 different sqlite3.dll, and this is the ideal load order: > > 1. C:\Web2py\sqlite3.dll -- bundled with web2py > 2. C:\Python25\DLLs\sqlite3.dll -- bundled with Python > 3. C:\Windows\System32\sqlite3.dll -- very old version installed by > unknown software (unpredictable)
