Re: [sqlite] Critical issue

2011-06-21 Thread Michael Stephenson
Hi Cyrille, You should probably use Dependency Walker on an end-user machine and profile your app with it to see what module(s) it cannot load. Since your app is 32bit, you'll need to get the 32bit version of Dependency Walker. Then, load your exe into DW, click on the Profile menu, and start

Re: [sqlite] Multiple Process problem

2011-06-21 Thread Igor Tandetnik
Thorsten Kersting wrote: > I try to write into a database with multiple processes, which can not > communicate to one another, beacause i start one programm many times. > When the program should write, it returns sqlite_busy. that i > understand. but then,

[sqlite] Multiple Process problem

2011-06-21 Thread Thorsten Kersting
I try to write into a database with multiple processes, which can not communicate to one another, beacause i start one programm many times. When the program should write, it returns sqlite_busy. that i understand. but then, every process return sqlite_busy, and it seems they are blocking

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread e-mail mgbg25171
David, Simon...that's good to know...Thank you very much indeed! On 21 June 2011 13:19, Simon Slavin wrote: > > On 21 Jun 2011, at 12:59pm, e-mail mgbg25171 wrote: > > > I was looking at prepare/step/finalise as a means of avoiding the > callback > > inherent in

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread Simon Slavin
On 21 Jun 2011, at 12:59pm, e-mail mgbg25171 wrote: > I was looking at prepare/step/finalise as a means of avoiding the callback > inherent in sqlite3_exec(). You do not need to use the callback if you don't want it to do anything. Just pass a NULL there. Simon.

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread David Bicking
Since none of the statements is a SELECT, as far as I know the callback would never be called. You can pass a zero as the callback address. get_table will also handle all the statements in one pass, but will return an empty able, so you might as well use exec. David On 06/21/2011 07:59 AM,

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread e-mail mgbg25171
Thank you Igor On 21 June 2011 12:52, Igor Tandetnik wrote: > e-mail mgbg25171 wrote: > > Howto...multi-sqlite command string through sqlite3_prepare_v2() to > create SINGLE statement > > You can't do that. > > > sql = "BEGIN"; //you need to

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread e-mail mgbg25171
Thank you for the clarification re... sqlite3_prepareXXX() only processing 1 statement at a time as opposed to sqlite3_exec() which... can handle "combined multi statements" in one shot. I was looking at prepare/step/finalise as a means of avoiding the callback inherent in sqlite3_exec(). In the

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread Igor Tandetnik
e-mail mgbg25171 wrote: > Howto...multi-sqlite command string through sqlite3_prepare_v2() to create > SINGLE statement You can't do that. > sql = "BEGIN"; //you need to add newline here > sql += "create table episodes (id integer primary key, season int, name >

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread David Bicking
On 06/21/2011 07:22 AM, e-mail mgbg25171 wrote: > The commented out lines work. > I'm wondering... > a) is it possible to do what's not commented out > b) what's the syntax re the "sql =..." and "sql +=..." lines > Any help much appreciated! > > > sql = "BEGIN"; //you need to add newline here >

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread e-mail mgbg25171
Thank you very much for the response. Unless I'm doing something foolish (always a possibility) that doesn't seem to work so... here's the whole test program. #include "stdafx.h" #include "sqlite3.h" #include "stdio.h" #include "string.h" #include "string" #include "iostream" using namespace

Re: [sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread Black, Michael (IS)
I believe this will work if you put the SQL-required semi-colons at the end of your statements. sql = "BEGIN;"; //you need to add newline here sql += "create table episodes (id integer primary key, season int, name text);"; sql += "insert into episodes(id, season, name) Values(1,2,'bill');";

Re: [sqlite] Help sqlite database corruption

2011-06-21 Thread Black, Michael (IS)
As I said before...welcome to DLL hell... You guessed itthe original DLL will give an error if any of the DLLs it depends on are not loadable. Since sqlite.interop.dll is non-standard you should include ALL DLLs that it depends on in your installation. Subject to Microsoft's

[sqlite] Howto...multi-sqlite command string through sqlite3_prepare_v2() to create SINGLE statement

2011-06-21 Thread e-mail mgbg25171
The commented out lines work. I'm wondering... a) is it possible to do what's not commented out b) what's the syntax re the "sql =..." and "sql +=..." lines Any help much appreciated! [code] //sql = "create table episodes (id integer primary key, season int, name text);"; rc =

Re: [sqlite] Help sqlite database corruption

2011-06-21 Thread Singh, Manpreet
Anyone with clues to the problem "malformed disk image"? From: Singh, Manpreet Sent: Tuesday, May 24, 2011 3:10 PM To: sqlite-...@sqlite.org; d...@hwaci.com; sqlite-users@sqlite.org Cc: Singh, Abhijeet; Singh, Satbeer; Prasanth, Neelapalem Subject: RE: Help sqlite database corruption

Re: [sqlite] Critical issue

2011-06-21 Thread Cyrille
Dear Michael, Thank you very much. I am currently working with my users to make some testing following your advice. It seems that so far, the users encountering the bug has IE 8 installed. However, I have on another computer IE9 and the desktop application is running perfectly. They ran