Hi Dan, You are right!!! I used the same handle (sqlite3_stmt *pStmt) for read and the insert. So when I read the data from the table I used the following code: sqlSt = sqlite3_prepare_v2(pDb,REMOTEWX_DB_SELECT,-1,&pStmt,0); while (!bFinished) { sqlSt = sqlite3_step(pStmt); iColCnt=0; switch (sqlSt) { case SQLITE_DONE: bFinished = true; sqlite3_reset(pStmt); // Resets the compited statement for re-use break; ...... sqlite3_finalize(pStmt); Then when I inserted the data to the table I used the same handle(pStmt) that caused this un-predictable problem. So Should I use two different handles. One for read and one for insert. Thanks, JP
----- Original Message ---- From: Dan <[EMAIL PROTECTED]> To: sqlite-users@sqlite.org Sent: Monday, January 21, 2008 8:19:49 PM Subject: Re: [sqlite] Program is crahed on sqlite3_bind_int- Could you please help On Jan 22, 2008, at 9:14 AM, Joanne Pham wrote: > Hi All, > I still had the problem below: >> sqlite3_bind_int64 (pStmt=0x40058a28, i=1, iValue=10) at ./src/ >> vdbeapi.c:897 >> 897 ./src/vdbeapi.c: No such file or directory. >> in ./src/vdbeapi.c >> Current language: auto; currently c > > when I used sqlite3_bind_int. I couldn't figure out what is the > problem and how to fit it. It used to work last week. > Could you please help. It's likely that the statement handle is invalid or has already been passed to sqlite3_finalize(). Dan. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] ----------------------------------------------------------------------------- ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping