Thanks for the replies so far.
I've been trying to get the database to lock - I am using a program I developed
which runs on 2 of my computers but connected to the same SQLite database:
mstrSQL = "PRAGMA locking_mode = EXCLUSIVE;BEGIN EXCLUSIVE;UPDATE
Utilities SET OwnersName = '" & Date.Now & "' WHERE RecNo = 1;COMMIT;"
On running this code (VB.Net), the record updates successfully, the message
'Done!" displays, no error message - but the same program on another computer
pointing to the same database across the network is still able to open the
database and run the program.
I have missed something - but what is it? Thanks for your help.
Jonathan
On 17 April 2013 14:39, J Trahair <j.trah...@foreversoftware.co.uk> wrote:
> Hi everyone
>
> Can my application lock the database for its own exclusive use at the
beginning of a series of INSERTs UPDATEs and SELECTs, then unlock it again
afterwards? I've read about the five locking states (unlocked, shared, etc.)
but I assume the dll handles all that at INSERT or UPDATE time. I'm looking for
a way to ensure other users aren't allowed to write to the database during this
quarter-second period.
http://www.sqlite.org/lang_transaction.html
BEGIN EXCLUSIVE
>
> Thanks in advance.
>
> Jonathan Trahair
Regards,
Simon
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
