Thanks.. That was just what I was looking for!!! Ken [EMAIL PROTECTED] wrote: Ken wrote: > sqlite3_step > sqlite3_finalize > sqlite3_reset > > Ok I think I know.. the reset should not have been called.
Right. Finalize is the destructor for the sqlite3_stmt object. Bad things happen when you try to call a method on an object which has already been destroyed. > What should one do if you get a SQLITE_BUSY on finalizing ???? If you use sqlite3_prepare_v2() then the result code is returned directly from sqlite3_step(). If you are using the legacy interface (sqlite3_prepare) or if you are ignoring the sqlite3_step() return code then call sqlite3_reset() to find the result. It is OK to call sqlite3_finalize() after sqlite3_reset(), if that is what you want to do. -- D. Richard Hipp ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
