Hello all, I'm very confused about a strange case. Maybe someone can lighten me up.
We have an application (a serial analyzer) which stores its project settings in a sqlite3 database file. Our application is statically linked with sqlite3.6 (build from the sources and with SQLITE_THREADSAFE=1). This works very well on all Linux and Windows systems over the years with - now - one first exception: On a certain customer system (Windows7 64bit) the application cannot read the example project files (created with sqlite3.6 library). And when the user stores his own settings in a new project, the project file is saved as a version 2.1 file (** This file contains an SQLite 2.1 database...) instead of a sqlite3 compatible file (SQLite format 3...) For me it at first seems that the sqlite calls are substituted by an older sqlite version. This would explain why the project reading fails (a sqlite3 file cannot read with an older sqlite version). In the same way the new project file is created as sqlite2.1. But because the sqlite functionality is part of the application (static linked), the program should never able to access an external sqlite DLL. I also traced the system/library calls with wintrc.exe but didn't see any hint for an external sqlite DLL access. So I just don't understand how this could happen. Have you heard about something similar? Thanks a lot for any explanation. Joachim Bürmann _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
