[sqlite] problem compiling std_call dll

2015-03-02 Thread Bart Smissaert
Thanks for clearing this up. I did wonder about this. Came across it when making a .tlb for those calls to the std_call dll. RBS On Mon, Mar 2, 2015 at 6:14 AM, Scott Robison wrote: > On Sun, Mar 1, 2015 at 10:55 PM, J Decker wrote: > > > On Sun, Mar 1, 2015 at 9:22 PM, Keith Medcalf > wrote

[sqlite] problem compiling std_call dll

2015-03-01 Thread James K. Lowden
On Sat, 28 Feb 2015 11:22:12 + Bart Smissaert wrote: > It doesn't compile and gives linking errors: > > Error 1 error LNK2001: unresolved external symbol > _sqlite3_db_filename > C:\Users\Bart\SQLiteForExcel\Source\SQLite3_StdCall > \SQLite3_StdCall.obj SQLite3_StdCall > Error 2 error LNK112

[sqlite] problem compiling std_call dll

2015-03-01 Thread Scott Robison
On Sun, Mar 1, 2015 at 10:55 PM, J Decker wrote: > On Sun, Mar 1, 2015 at 9:22 PM, Keith Medcalf wrote: > > > >I do not know if this is the case, but typically Windows creates names > > >like > > >_sqlite3_db_filename at X (where X is a number) if a function is defined > as > > >stdcall. It does

[sqlite] problem compiling std_call dll

2015-03-01 Thread Scott Robison
On Sun, Mar 1, 2015 at 10:22 PM, Keith Medcalf wrote: > >I do not know if this is the case, but typically Windows creates names > >like > >_sqlite3_db_filename at X (where X is a number) if a function is defined as > >stdcall. It doesn't *have* to do this, but that's the convention used by > > th

[sqlite] problem compiling std_call dll

2015-03-01 Thread Keith Medcalf
>I do not know if this is the case, but typically Windows creates names >like >_sqlite3_db_filename at X (where X is a number) if a function is defined as >stdcall. It doesn't *have* to do this, but that's the convention used by the @X is used to include the ordinal reference (@X) in the symbol s

[sqlite] problem compiling std_call dll

2015-03-01 Thread J Decker
On Sun, Mar 1, 2015 at 9:22 PM, Keith Medcalf wrote: > >I do not know if this is the case, but typically Windows creates names > >like > >_sqlite3_db_filename at X (where X is a number) if a function is defined as > >stdcall. It doesn't *have* to do this, but that's the convention used by > > the

[sqlite] problem compiling std_call dll

2015-03-01 Thread Scott Robison
On Sun, Mar 1, 2015 at 9:28 PM, James K. Lowden wrote: > On Sat, 28 Feb 2015 11:22:12 + > Bart Smissaert wrote: > > > It doesn't compile and gives linking errors: > > > > Error 1 error LNK2001: unresolved external symbol > > _sqlite3_db_filename > > C:\Users\Bart\SQLiteForExcel\Source\SQLite

[sqlite] problem compiling std_call dll

2015-03-01 Thread Bart Smissaert
Iooked at that underscore (in _sqlite3_db_filename) as well, but that is just how VS presents the error, it didn't find a faulty underscore in the code. So, that is not it. As far as I can see the SQLite3 functions in this project are only in 3 places: sqlite3.h, SQLite3_StdCall.c and in the .def f

[sqlite] problem compiling std_call dll

2015-03-01 Thread Teg
Hello Bart, dumpbin /all sqlite3.obj > sqlite.txt You can then look at the sqlite.txt file with a text editor. I found _sqlite3_db_filename listed in there a couple times. That tells you it was probably compiled in. If you can't find it then that could be part of the problem. Then I might dump t

[sqlite] problem compiling std_call dll

2015-03-01 Thread Amit Chaudhuri
Bart, you say "don't know anything about C or C++ or compiling C code" Perhaps this will help. The error message (unresolved) external means that the linker is trying to find something (_sqlite3_db_filename in this case) but it cannot. Possible common causes include - it has been misspelt (I'm l

[sqlite] problem compiling std_call dll

2015-02-28 Thread Bart Smissaert
Trying to compile a std_call dll to be used with VB6 and VBA. Using instructions and files from this website: https://sqliteforexcel.codeplex.com/ All works well and have added a few SQLite functions that weren't in the compiled dll as in the download section from that website. However having probl