Hello PokerAce, Wednesday, November 7, 2007, 12:07:49 PM, you wrote:
P> I'm using version 3.5.2. I built the static library using MSVC++ 6. The P> debug build works great. However, when I use the release build, the connect P> works, but every SQL statement I try to execute returns "SQL logic error or P> missing database." I know it's not a configuration problem between the P> debug and release builds of my program, because if I link the debug build of P> SQLite into the release build of my application, everything works great. P> I log the SQL statements before they are executed and they are fine. I P> check the name of the db file before connecting to it, and that's fine. I P> checked the build options between the Debug and Release builds of SQLite and P> other than the standard differences, nothing stands out. P> Anyone experience anything like this before? P> I should also mention that I was previously using version 3.3.8 with the P> exact same build settings and it worked fine. I'd probably start by cutting back on the optimizations and see what happens. I'd never had "whole program" optimization work without breaking my code for example. I'd leave it in release build, select all the projects and disable optimization and see if it works. Release and Debug builds can often have different results. Debug builds initialize variables which release builds don't. Happens to me all the time. You can also build debug INTO a release build by setting the options in the compiler and linker tabs. I do that from time to time when I have weird release build issues. If the optimizer's being used, you'll be hopping around the code unexpectedly but, you can still get the jist of what's going on. -- Best regards, Teg mailto:[EMAIL PROTECTED] ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
