Does this mean that you are trying to link the LIB with the OTHER COPY of sqlite into the same application tht is using the DLL, because this sure sounds like what you are doing. In which case the versions are NOT independant processes soince they are both linked to the same process, or to both processes.
> -----Original Message----- > From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users- > bounces at mailinglists.sqlite.org] On Behalf Of Rail Jon Rogut > Sent: Tuesday, 5 April, 2016 21:55 > To: SQLite mailing list > Subject: Re: [sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL > > Hi Simon, > > Thanks for replying. > > To clarify -- if I run this configuration with the 3rd party LIB I get the > error. If I run my program (DLL) without the 3rd party LIB my database > works perfectly fine -- so the disk isn't corrupted and the database > itself is fine. It's only while running my program with the 3rd party DLL > sqlite database open that I get the error. > > Yes - these are completely separate databases -- the 3rd party DLL is > creating a database while it's running. My database is only trying to > read and failing. The two Sqlite processes 'should' be completely > separate -- and neither cares about the other so no trying to share code > or data at all. > > So to summarize... there's no disk corruption and the databases are fine. > > Thanks, > > Rail > --------------------------------- > > On Apr 5, 2016, at 6:43 PM, Simon Slavin <slavins at bigfraud.org> wrote: > > > > > On 6 Apr 2016, at 2:11am, Rail Jon Rogut <sqlite3 at platinumsamples.com> > wrote: > > > >> sql = pragma table_info('mytablename'); > >> Sqlite3 log: 3338 Err: os_win.c:37516: (0) > winAccess(C:\MyAppPath\Databases\mydatabase.db-journal) - The operation > completed successfully. > >> Sqlite3 log: 3338 Err: disk I/O error > > > > Presumably you mean that if you try the same thing and the other program > isn't running, you get no problem. And that the problem does occur > without fail when the other program is running. > > > > Also, just because it's so unusual I just want you to restate that these > two programs are trying to open different databases. At least that's what > I understood from your post. > > > > Please can you run whatever tools your OS provides for checking disk > formatting and directory structure, just to ensure that your problem is > not caused by a corrupt disk. > > > > Can you write some code which tries to open the database file(s) just > using plain file commands (presumably fopen() or something like that) ? > Does this code also get 'disk I/O error' ? > > > > Another thing to try would be to download the SQLite shell tool and try > using that to open the database instead. Do you get the same problem ? > > > > Simon. > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users at mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
