On Jun 15, 9:12 pm, Yarko Tymciurak <resultsinsoftw...@gmail.com> wrote: > 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 got an unexpected result. C:\Python25\python.exe loads C:\Python25\Dlls\sqlite3.dll when I issue "import sqlite3" And, C:\web2py\web2py.exe loads C:\Windows\system32\sqlite3.dll immediately (before pressing Start Server button.) FWIW, in my Win32 apps, I specify the full path when calling LoadLibrary() for DLLs bundled with my app. I usually grab the current process's .exe path and then prefix that to DLL names. Otherwise, I have to deal with the insanity of Windows having multiple different DLL search orders depending on external factors as described here: Dynamic-Link Library Search Order http://msdn.microsoft.com/en-us/library/ms682586(VS.85).aspx Makes me want to throw Windows out the window.