Suspect you are running into more VBA<->C issues. The db path, journal path
and wal path are stored sequentially in memory, so if you were to skip the
NUL terminators you'd see all three paths.
But I'm not exactly sure how that might happen without resulting in a
segfault, so I could be missing so
orth
> Date: 09/10/2015 09:52 (GMT+00:00)
> To: General Discussion of SQLite Database <
> sqlite-users at mailinglists.sqlite.org>
> Subject: Re: [sqlite] Problem with sqlite3_db_filename
>
> Suspect you are running into more VBA<->C issues. The db path, journal pa
Thanks for that. Must indeed be a C > VBA problem and will sort this out.
RBS
On Fri, Oct 9, 2015 at 9:52 AM, Rowan Worth wrote:
> Suspect you are running into more VBA<->C issues. The db path, journal path
> and wal path are stored sequentially in memory, so if you were to skip the
> NUL termi
All working fine now, but noticed that for the attached database I get not
just the file path of the attached database, but also the journal
file path and wal file path:
C:\Test\NewDB2.db3C:\Test\NewDB2.db3-journalC:\Test\NewDB2.db3-wal
There is actually no journal file or wal file that I can see
Ignore this as I know what the problem was.
I was passing a pointer to the Unicode string, but should be pointer to
8bit ASCII string.
RBS
On Thu, Oct 8, 2015 at 9:58 AM, Bart Smissaert
wrote:
> OK, thanks, at least I know that the function works fine then in
> sqlite3.dll.
> Problem must be on
On 10/08/2015 03:51 AM, Bart Smissaert wrote:
> As I understand it this should produce a filepointer to the filepath of the
> attached database, given the database handle of file the other database was
> attached to and the database name of the attached database. I checked all
> the return values a
OK, thanks, at least I know that the function works fine then in
sqlite3.dll.
Problem must be on my side then.
This is the code in the Std_Call dll:
SQLITE3_STDCALL_API const char * __stdcall sqlite3_stdcall_db_filename(sqlite3
*pDb, const char *zDbName)
{
return sqlite3_db_filename(pDb, zDbN
As I understand it this should produce a filepointer to the filepath of the
attached database, given the database handle of file the other database was
attached to and the database name of the attached database. I checked all
the return values and also did a select involving tables in both
database
9 matches
Mail list logo
