Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
microsoft.public.vb.database
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
database corruption Access 2000 with VB
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   4 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Klaus Lohse  
View profile  
 More options Feb 8 2001, 5:18 am
Newsgroups: microsoft.public.vb.database
From: "Klaus Lohse" <i...@Lohse.de>
Date: Thu, 8 Feb 2001 11:13:03 +0100
Local: Thurs, Feb 8 2001 5:13 am
Subject: database corruption Access 2000 with VB
Print | Individual message | Show original | Report this message | Find messages by this author
Hi to all,
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 (i...@Lohse.de)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mark Foster  
View profile  
 More options Feb 8 2001, 5:38 am
Newsgroups: microsoft.public.vb.database
From: "Mark Foster" <ma...@anchor.co.uk>
Date: Thu, 8 Feb 2001 10:34:11 -0000
Local: Thurs, Feb 8 2001 5:34 am
Subject: Re: database corruption Access 2000 with VB
Print | Individual message | Show original | Report this message | Find messages by this author

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" <i...@Lohse.de> wrote in message

news:OS$1XdbkAHA.2168@tkmsftngp03...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Steve Liang  
View profile  
 More options Feb 11 2001, 2:19 am
Newsgroups: microsoft.public.vb.database
From: steveliangNoS...@microsoft.com (Steve Liang)
Date: Sun, 11 Feb 2001 07:18:28 GMT
Local: Sun, Feb 11 2001 2:18 am
Subject: RE: database corruption Access 2000 with VB
Print | Individual message | Show original | Report this message | Find messages by this author
Hi Klaus,

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jordi Gomis  
View profile  
 More options Feb 13 2001, 1:11 pm
Newsgroups: microsoft.public.vb.database
From: "Jordi Gomis" <j...@acigrup.com>
Date: Tue, 13 Feb 2001 19:12:44 +0100
Local: Tues, Feb 13 2001 1:12 pm
Subject: Re: database corruption Access 2000 with VB
Print | Individual message | Show original | Report this message | Find messages by this author
I have de same problem.
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" <i...@Lohse.de> escribió en el mensaje
news:OS$1XdbkAHA.2168@tkmsftngp03...


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google