Re: [sqlite] Database opens OK but further calls result in MISUSE

2005-06-24 Thread Jay Sprenkle
> Apparently not. The sqlite3_open function was OK, but all the others > weren't - I thought it was the other way around. I sent the email to > the list, went to bed, then when I woke up I knew what was wrong. > Sorry for the trouble. I figure out things in dreams too. > > On the other hand,

Re: [sqlite] Database opens OK but further calls result in MISUSE

2005-06-24 Thread Jay Sprenkle
> > --- > > rc = sqlite3_open("test.db", db) > > You are not passing the correct arguments to sqlite3_open. The > compiler should have noticed this... > > If you are declaring the variable db like "sqlite3 *db;" you have to > call sqlite3_open like: > rc = sqlite3_open("test.db", ); > > That

Re: [sqlite] Database opens OK but further calls result in MISUSE

2005-06-24 Thread Tiago Dionizio
On 6/23/05, James Arthur <[EMAIL PROTECTED]> wrote: > I've started with something fairly simple - opening and closing a database. > --- > rc = sqlite3_open("test.db", db) You are not passing the correct arguments to sqlite3_open. The compiler should have noticed this... If you are declaring the

Re: [sqlite] Database opens OK but further calls result in MISUSE

2005-06-24 Thread Jay Sprenkle
> rc = sqlite3_open("test.db", db) > If Not rc=SQLITE_OK > Print("Can't open database "+rc) > sqlite3_close(db) > End > Else > Print("Opened: "+rc) > EndIf > > Print("Errcode: "+sqlite3_errcode(db)) Why are you asking for the error code when you already know there was no error? (

[sqlite] Database opens OK but further calls result in MISUSE

2005-06-23 Thread James Arthur
Hi I'm trying to write a SQLite module for BlitzMax (www.blitzmax.com) and have run in to some difficulty. I've taken the "pure C source" sqlite-source-3_2_2.zip file and mapped the C functions directly to Max functions (Max produces *.s code and then uses GCC to compile and link those and any