Use explicit paths to where your database is opened from. Depending on where the application is run from, from the debugger even, it may launch the application from one place, but set its running directory to another. So your application may be trying to read the database file from somewhere you're not expecting.
On Mon, Mar 6, 2017 at 10:34 AM, Rob Richardson <[email protected]> wrote: > Greetings! > > I used SQLite in a successful program a few years ago. I am trying to > resurrect that program for a new customer, but it isn't working, and I'm > having a hellish time trying to debug it. > > I have a Windows 7 XP1 OS, and I'm using Visual Studio 2008, which is what > the original program was built with. > > The original program builds an ActiveX control. I have a web page (HTML > file) that includes the control. I can build the control in debug mode, > load the web page in Internet Explorer, and the control works. It opens an > SQLite database, tries to prepare a statement, and throws an error > complaining that a table does not exist, even though it does. The SQL > statement and the SQLite file are unchanged from the version that is > running at the old customer site. > > I have stripped out the SQLite code into a separate project so that I can > run it by itself, and hopefully step through it in a debugger. However, > when I try to run it, I get the following message: > > "The application was unable to start correctly (0xc000007b). Click OK to > close the application." > > I have a feeling this is related to 32-bit vs 64-bit applications, but I'm > not sure. What do I need to do to get this little test program to run? > > Thank you very much. > > Rob Richardson > _______________________________________________ > sqlite-users mailing list > [email protected] > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
