[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread R Smith
On 2016/01/23 9:41 PM, Bart Smissaert wrote: > Using a .tlb file to access the sqlite3 functions from VB6. > Sofar when the arguments of the sqlite3 function are declared as int I have > been using > long in the IDL source to compile the tlb and this has been fine. I'm not very familiar with

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Bart Smissaert
> I am somewhat confused about what you wrote. This has to do with making a .tlb (type library) to access sqlite3.dll from a VB6 ActiveX dll. This type library is made by compiling (with midl) an .idl source file. In this .idl file I need to map the SQLite data types with IDL data types. Sofar I

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Bart Smissaert
Using a .tlb file to access the sqlite3 functions from VB6. Sofar when the arguments of the sqlite3 function are declared as int I have been using long in the IDL source to compile the tlb and this has been fine. sqlite3_compileoption_get is defined like this: const char

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Keith Medcalf
> I am somewhat confused about what you wrote. SQLite provides a C > level api. You can ignore the types and put in alternatives. > Depending on byte order, calling conventions, what the C types > actually mapped to, sizes of types etc it may work when wrong anyway, > or you could get seriously

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/16 17:36, Bart Smissaert wrote: > What is different though about sqlite3_compileoption_get, so that > long in the IDL causes the mentioned problems and int doesn't? Absolutely nothing is different about that API. If something was then one

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/16 13:14, Bart Smissaert wrote: >> I am somewhat confused about what you wrote. > > This has to do with making a .tlb (type library) to access > sqlite3.dll from a VB6 ActiveX dll. That much was clear. > Sofar I have mapped SQLite int with

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Scott Robison
On Sat, Jan 23, 2016 at 2:18 PM, R Smith wrote: > > > On 2016/01/23 9:41 PM, Bart Smissaert wrote: > >> Using a .tlb file to access the sqlite3 functions from VB6. >> Sofar when the arguments of the sqlite3 function are declared as int I >> have >> been using >> long in the IDL source to compile

[sqlite] Slight problem with sqlite3_compileoption_get

2016-01-23 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/16 11:41, Bart Smissaert wrote: > My question is how could I have foreseen this problem, so how could > I have known that using long is no good here? I am somewhat confused about what you wrote. SQLite provides a C level api. You can

[sqlite] Sqlite and we7 local time issue

2016-01-23 Thread Gunnar Roth
Hello, does anybody use sqlite with we7? The problem is that wec7 is missing the localtime function, but there is replacement code for windows ce in sqlite , but no prototype. So when i build i get still a linker error for localtime as localtime is used before it is defined and that usage

[sqlite] .mode defaults

2016-01-23 Thread Klaas V
Ciao SQLiters, The separators don't change back to the defaults automatically after change of mode from 'asci' to 'list'. Perhaps a '.mode def' or something like that would help to do so? Defaults --[[z4us|binz--]] sqlite3 o1.sqc '.sho' ? ? ? ? echo: off ? ? ? ???eqp: off ? explain: off ?