On Windows you will get a console and standard output if you are running a
console application, and otherwise not.
I think you need a simple console app to call your ActiveX DLL, or find some
other way. Windows GUI app and standard output do not play well together.
Regards
David M Bennett FACS
A
> 1) Click Start etc.
That won't show the debug output.
Wish it was that simple.
> If you want to prove your dll is working (or not
> working), you should attempt to isolate it, for direct testing.
Not sure what you mean with that. I know an error occurs in sqlite3.dll and
hopefully the debug ou
Will look at this, it is a VB6 console app and that may just do the job:
http://vb.mvps.org/samples/Console/
RBS
On Wed, Dec 9, 2015 at 1:03 PM, wrote:
> On Windows you will get a console and standard output if you are running a
> console application, and otherwise not.
>
> I think you need a s
On Windows you will get a console and standard output if you are running a
console application, and otherwise not.
I think you need a simple console app to call your ActiveX DLL, or find some
other way. Windows GUI app and standard output do not play well together.
Regards
David M Bennett FACS
A
"This is on a Win7 machine. How do I bring up that console window?"
1) Click Start
2) type cmd
you will see cmd.exe in the list of programs to run.
3) click on cmd.exe
To run MS-excell from the command line, you can call it from the full
path (check version):
"C:\Program Files\Microsoft Office\O
On Wed, Dec 9, 2015 at 12:59 PM, Graham Holden
wrote:
> If you have, or create, a VB6 standalone EXE that calls SQLite, you should
> be possible to get it to show stdout/stderr.
>
OP already explained VB code is wrapped in an ActiveX dynamically
used/loaded by MS Excel.
So no user-controlled EX
If all else fails it would be no problem to write a little VB6 exe that
calls the ActiveX dll.
Not much code should be needed in that to reproduce that crash situation.
Would something like the free DOSBox do the job? Will try later.
RBS
On Wed, Dec 9, 2015 at 12:12 PM, Dominique Devienne
wrot
00:00)
To: SQLite mailing list
Subject: Re: [sqlite] How to see SQLite debugging information
> Are you using Excel or VB6?? They're very different things.
I use both. Have done for many years and by now I did indeed figure out
they are not the same :)
> freopen etc.
Thanks, will give th
On Wed, Dec 9, 2015 at 10:14 AM, Adam Devita wrote:
> To run MS-excell from the command line, you can call it from the full
> path (check version):
>
> "C:\Program Files\Microsoft Office\Office15\Excel.exe"
You can also run "start excel" to launch the current version of Excel.
Both of these are n
On Wed, Dec 9, 2015 at 3:50 AM, Richard Hipp wrote:
> On 12/8/15, Bart Smissaert wrote:
> > So, what/where is that standard output channel?
> SQLite does not have any facilities for debugging in a GUI on Windows.
Any chance to add a way to redirect debugging / troubleshooting output to a
file
That would be very useful and I take it wouldn't be difficult to add.
RBS
On Wed, Dec 9, 2015 at 7:53 AM, Dominique Devienne
wrote:
> On Wed, Dec 9, 2015 at 3:50 AM, Richard Hipp wrote:
>
> > On 12/8/15, Bart Smissaert wrote:
> > > So, what/where is that standard output channel?
> > SQLite
> The standard output is what displays on your screen when you are in a DOS
box.
OK, thanks, will look into that.
RBS
On Wed, Dec 9, 2015 at 2:50 AM, Richard Hipp wrote:
> On 12/8/15, Bart Smissaert wrote:
> > So, what/where is that standard output channel?
> > This is on a Win7 machine. How
> Are you using Excel or VB6? They're very different things.
I use both. Have done for many years and by now I did indeed figure out
they are not the same :)
> freopen etc.
Thanks, will give that a try.
> can step through the sqlite code in a debug build
That would be great, but not sure how tha
On 9 Dec 2015, at 12:45am, Bart Smissaert wrote:
> Surely there must be simple way to dump debugging data to say a text file.
Sure. Run Excel as a command rather than launching it in the Windows GUI.
Simon.
On 9 Dec 2015, at 12:45am, Bart Smissaert wrote:
> Excel doesn't do much, all the real work is done by that ActiveX dll and I
> have full access to that as I coded that.
> Surely there must be simple way to dump debugging data to say a text file.
Sure. Run your own program, not one someone els
Excel doesn't do much, all the real work is done by that ActiveX dll and I
have full access to that as I coded that.
Surely there must be simple way to dump debugging data to say a text file.
RBS
On Wed, Dec 9, 2015 at 12:37 AM, Simon Slavin wrote:
>
> On 9 Dec 2015, at 12:35am, Bart Smissaer
On 9 Dec 2015, at 12:35am, Bart Smissaert wrote:
> So, do I need to somehow re-direct this output to a text file?
I don't think it can be done. If the actual program you're running is Excel
then you're relying on Excel to do this stuff. And since Excel is a
spreadsheet program and not a dev
So, do I need to somehow re-direct this output to a text file?
RBS
On Wed, Dec 9, 2015 at 12:32 AM, Simon Slavin wrote:
>
> On 9 Dec 2015, at 12:30am, Bart Smissaert
> wrote:
>
> > So, what/where is that standard output channel?
> > This is on a Win7 machine. How do I bring up that console w
On 9 Dec 2015, at 12:30am, Bart Smissaert wrote:
> So, what/where is that standard output channel?
> This is on a Win7 machine. How do I bring up that console window?
> There is no development environment here. I am running this from Excel.
Then Excel is getting the output. And since Excel is
So, what/where is that standard output channel?
This is on a Win7 machine. How do I bring up that console window?
There is no development environment here. I am running this from Excel.
So, I have a standard Windows sqlite3.dll, a std_call dll (to make SQLite
accessible to VB6)
a .tlb file an Activ
On 8 Dec 2015, at 10:18pm, Bart Smissaert wrote:
>> on standard output
> But how this work in concrete steps? Does code have to be added to SQLite
> to write for example to a text file?
SQLite sends text to the standard output channel while your program is making
SQLite calls.
You should be a
> You did you manage to implement new UDFs if you are not a C programmer?
I forgot to say that the actual callback functions (the actual code that
performs the manipulations) is not in SQLite, but in that ActiveX dll.
RBS
On Tue, Dec 8, 2015 at 10:09 PM, Richard Hipp wrote:
> On 12/8/15, Bart
> on standard output
But how this work in concrete steps? Does code have to be added to SQLite
to write for example to a text file?
The Explain command doesn't produce this information or can it?
> You did you manage to implement new UDFs if you are not a C programmer?
Somebody familiar with C add
On 12/8/15, Bart Smissaert wrote:
> So, what/where is that standard output channel?
> This is on a Win7 machine. How do I bring up that console window?
>
The standard output is what displays on your screen when you are in a DOS box.
SQLite does not have any facilities for debugging in a GUI on W
Having a problem where 2 UDF's in one SQL cause a crash in my application
(Excel)
originating from SQLite. This is on Windows 7 with the latest SQLite
version.
I have a sqlite3.dll compiled with these compiler options:
-DSQLITE_DEBUG
-DSQLITE_MEMDEBUG
-DSQLITE_OMIT_LOOKASIDE
I can run PRAGMA vdbe
On Tue, Dec 8, 2015 at 4:30 PM, Bart Smissaert
wrote:
> So, what/where is that standard output channel?
> This is on a Win7 machine. How do I bring up that console window?
> There is no development environment here. I am running this from Excel.
> So, I have a standard Windows sqlite3.dll, a std_
On 12/8/15, Bart Smissaert wrote:
> Having a problem where 2 UDF's in one SQL cause a crash in my application
> (Excel)
> originating from SQLite. This is on Windows 7 with the latest SQLite
> version.
> I have a sqlite3.dll compiled with these compiler options:
>
> -DSQLITE_DEBUG
> -DSQLITE_MEMDE
27 matches
Mail list logo
