Canter
01-28-2008, 07:30 PM
I'm having a problem accessing an sqlite database under the following scenario:
The build is a single exe file, but I'm keeping the database file separate so that it can be modified (as opposed being in a temp file). I get the installation path from the registry, and use that plus the sqlite file name as the file paramater in the sqlite.open function. No errors are generated, but the database isn't accessed either. The only way I've been able to access it is to just build to a folder on the hard drive - and access it from paths such as _Sourcefolder, as opposed to the single exe.
Any ideas what I'm missing here? I don't understand why no errors are generated - the application acts as if it did read/write to the db - only it does neither.
Thanks for any suggestions.
The build is a single exe file, but I'm keeping the database file separate so that it can be modified (as opposed being in a temp file). I get the installation path from the registry, and use that plus the sqlite file name as the file paramater in the sqlite.open function. No errors are generated, but the database isn't accessed either. The only way I've been able to access it is to just build to a folder on the hard drive - and access it from paths such as _Sourcefolder, as opposed to the single exe.
Any ideas what I'm missing here? I don't understand why no errors are generated - the application acts as if it did read/write to the db - only it does neither.
Thanks for any suggestions.