I can confirm that the problem only exist when the database is encrypted.
On Sat, Sep 15, 2012 at 11:00 AM, Serge Fournier <tech...@gmail.com> wrote:
> I work with an encrypted database and it look like it could be part of the
> problem.
>
>
> On Wed, Sep 12, 2012 at 3:
Doing more testing on this I can say that I have the same problems with
Windows 7.
On Wed, Sep 12, 2012 at 8:08 AM, Serge Fournier <tech...@gmail.com> wrote:
> The thing here is that my code was working perfectly with the prior
> version of the library and Windows 7.
> The same c
o before you did all of the
>above instructions.
>7. *You are done!*
>
> *Brandon Sky Pimenta*
>
>
> On Tue, Sep 11, 2012 at 10:35 AM, Serge Fournier <tech...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I'm not sure if it's Windows 8 or the latest vers
SQLiteException
MessageBox.Show(sqlexception.Message, "Error!", MessageBoxButtons.OK,
MessageBoxIcon.Error)
Catch ex As Exception
MessageBox.Show(ex.Message, "Error!", MessageBoxButtons.OK, MessageBoxIcon
.Error)
End Try
It gives the "Still SQL queries to process" error.
send
a VACUUM pragma to it.
Simply put, it's only possible to open a database once in the application
for writing; it's like the lock
doesn't get released until the application is closed.
On Tue, Sep 11, 2012 at 5:59 PM, Joe Mistachkin <sql...@mistachkin.com>wrote:
>
> Serge Fournier w
Hi,
I'm not sure if it's Windows 8 or the latest version of the library
(1.0.82) but I have a new
problem with the same code that was working before.
Simply put, i I open a database and then close it in an application then I
reopen it again,
I cannot write to it anymore; it is always locked. I
6 matches
Mail list logo
