Solved this myself so no help needed. Apparently the problem was last parameter in sqlite3_prepare_v2 which was pointing to unallocated memory after execution. As NULL is allowed, I simply put it to NULL to ignore it which solved the whole thing.
That kind of explains all the spooky behaviour as obviously, additing additional statements moved the pointer in memory. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
