I work with an encrypted database and it look like it could be part of the
problem.

On Wed, Sep 12, 2012 at 3:05 PM, Serge Fournier <tech...@gmail.com> wrote:

> 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 code with 1.0.82 and Windows 8 doesn't work anymore.
>>
>> I cannot use your solution, because the way my appliation works; it
>> creates the database at first run and
>> miust be able to run on many computers.
>>
>> I've tried recreating the database; and so many things; the only thing
>> that works is to only
>> open the database once in my application which is no a good solution for
>> me since I have to
>> remove some functions like VACUUM etc...
>> Thanks.
>> On Tue, Sep 11, 2012 at 3:18 PM, Brandon Pimenta <
>> brandonskypime...@gmail.com> wrote:
>>
>>> I've experienced this problem in the past. According to
>>> here<http://technosophos.com/node/242>,
>>> I found a solution.
>>>
>>> *Brandon's Tips on How to Unlock SQLite Databases*
>>>
>>>    1. Open a command line prompt window.
>>>    2. Type *sqlite* *dbname*.sqlite in the command line prompt, replacing
>>>    "dbname" with the SQLite database name.
>>>    3. In the secondary prompt that appears, type *.backup* full *dbname*
>>>    .sqlite, replacing "dbname" with the SQLite database name.
>>>    4. Type *.exit *to return to the ordinary command prompt.
>>>    5. Type *mv* *dbname*.sqlite old.sqlite, then *mv* backup.sqlite
>>> *dbname*
>>>    .sqlite in the command line, replacing "dbname" with the SQLite
>>> database
>>>    name.
>>>    6. Try the task you were attempting to do 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 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 tried doing a
>>> close,
>>> > dispose and shutdown
>>> > to my connection and then reopning it and do a simple vaccum; it tell
>>> me
>>> > that there's still
>>> > sql queries in progress when none were sent to the database.
>>> >
>>> > I cannot test this in Windows 7 yet, but I'm wandering if it's a
>>> problem
>>> > with Windows 8; or
>>> > a bug in the new version of System.Data.SQlite.
>>> >
>>> > I use Visual Studio 2010.
>>> >
>>> > Thanks.
>>> > _______________________________________________
>>> > sqlite-users mailing list
>>> > sqlite-users@sqlite.org
>>> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>>> >
>>> _______________________________________________
>>> sqlite-users mailing list
>>> sqlite-users@sqlite.org
>>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>>>
>>
>>
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to