Gerry Snyder wrote:
Steve Bergman wrote:
Yeah, I know my post was light on details and pretty general.
Basically, at this point I was wondering if anyone had any general
advice. Although I'm pretty sure I have seen this problem when I am
the only one in the application, the application has been in
development, meaning I've been getting (unrelated) fatal errors,
stopping and restarting the app, etc. which could well be the cause
of what I have seen.
The stand-alone SQLite executable can be used to help tell whether the
database file has been put into a locked state, or whether all the
problem is in your program. Maybe you've used it already.
When I see the problem, I can immediately retry the operation and it
succeeds. As of today, the app is in production mode and being used by
a small number of people, so I should have a better idea what the status
is by the end of the day.
Thanks,
Steve
