Using VB6, an Access DB and ADODB, What is the correct method of handling DB locking in a network?
Posted on 2003-11-08
I have an application which runs on a network sharing a common database.
It's written in VB6 using ADODB for connectivity to an Access 2000 DB.
It runs on 4 PCs and about once or twice a week I get the following error (or similar)
-2147467259 The table 'tblStaff' is already opened exclusively by another user,
or it is already open through the user interface and cannot be manipulated programmatically.
Im using Optimistic locking.
If I get a DB related error I resume for 5 times on the failing command in the hope that the lock will be released by then but this doesnt catch the above error.
Can any one tell me the correct method of handling table/record locking using ADODB ?
(I've used DAO in the past and I rearly had problems)
Peculiarily enough, this error only hanppens on one PC (the fastest one on the network).
Any help with this would be much appreciated.