Igor: You're right. Thanks you and congratulations on your fine smell.
As indicated in the OP, indeed I was using relative path with the "original" table. I wish I had thought before, especially, because I remember that some time ago, I had problems for the same reason, it seems, Visual Studio has some problems with the address of the current working directory. In fact, it uses different directories according to the "Debug" or "Release" mode used. Thank you again. -- Adolfo J. Millan > > ---- Mensaje original ---- > De: Igor Tandetnik <i...@tandetnik.org> > Para: sqlite-users@sqlite.org > Fecha: Fri, 11 Jan 2013 14:49:23 +0100 > Asunto: Re: [sqlite] Problem whit sqlite_prepare_v2() in 3.7.5 > versionandlater > > > >On 1/11/2013 5:34 AM, a...@zator.com wrote: >> Problem (partially) solved: >> >> Using MS Windows 8; MS Visual Studio 2012 for desktop, and SQLite 3.7.15.1 I >> get consistently the following behavior for the application: >> >> Running in Debug-mode, fails as reported in the OP. >> >> Running in Release-mode (without debugging), fails as reported. >> >> Starting the resulting executable as stand-alone -from the desktop or from >> the CLI-, run as expected without error. > >Current working directory is different in these cases. I bet you are >using relative paths in your statements. In which case it's a simple >matter of SQLite using the right database file sometimes, but creating a >blank new one other times. >-- >Igor Tandetnik > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
