database corruption Access 2000 with VB
Klaus Lohse
One of my customer works with an Access 2000 Database via Visual Basic
Client programs. The database resides on a NT-Server (4.0) and all the
clients have Win 2000 Professional on a Pentium III computer with the
exception of one computer that is a Pentium 133 with Windows NT 4.0 Service
Pack 6. The network is Ethernet currently running with a 10MB switch, we
have 10 clients.
From time to time the database gets corrupted (after 4 or 5 days), we do not
know when cause all clients which work with the database can continue the
work. Only clients which log into the database get the "database is
corrupted" error. After a database repair all things do well until ..
Some parts of the client software worked with DAO, most parts worked with
ADO, so we decided to clean up the source code and use only ADO, but now the
database gets corrupted daily.
I have customers that work with similar programs sharing a lot of the source
code and no one of them has this problem, these databases never corrupt.
Klaus (in...@Lohse.de)
Mark Foster
We had this problem a lot with our clients using our vb app and an access
database. We tracked it down to earlier parts of the code where the database
wasn't getting closed in certain areas. Since we tidied up the code and made
sure all references were set to nothing, then the problem has virtually
disappeared.
"Klaus Lohse" <in...@Lohse.de> wrote in message
news:OS$1XdbkAHA.2168@tkmsftngp03...
Steve Liang
Generally speaking, Access in not a backend database that would work
perfectly in the multi-user environment.
To increase the performance and reduce the errors, I suggest you:
1. release the resource as early as possible, such as the connection,
recordset, etc.
2. use pessimistic lock or readonly lock instead of the optimistic lock
If you have a specific error, I suggest you contact Microsoft Developer
Support. They will work with you on the problem more efficiently.
Steve
Jordi Gomis
I use first the DAO 3.51 and Vb5.0 and all works fine. When i use DAO 3.60
and Vb6.0 the problem begans. I put the DAO 3.51 and Vb6.0 and the problem
seems to be resolved. I am not sure because i didi it last friday.
"Klaus Lohse" <in...@Lohse.de> escribió en el mensaje
news:OS$1XdbkAHA.2168@tkmsftngp03...