ACC2000-Compact and Repair frequently

  • Thread starter Thread starter Greg Hill
  • Start date Start date
G

Greg Hill

My access 2000 database is on a shared network drive. It
works fine for a while with multiple users in it, but it
eventually will need to be compacted and repaired. This
has happened 5 times just today, and another 3 yesterday.
I have seen as many as 10 people in it at one time, but I
don't think that it the problem. Any help is
apprecitated!!! Thanks in advance!
 
Greg Hill said:
My access 2000 database is on a shared network drive. It
works fine for a while with multiple users in it, but it
eventually will need to be compacted and repaired. This
has happened 5 times just today, and another 3 yesterday.
Click to expand...

What has happened? If you mean Access reports that the filed *needs* to be repaired
then that is not good or normal. You should not have users opening the same shared
application file like that . It greatly increases the chances of the file getting
corrupted. You should split the file and give each user a local copy of the front
end and only share the data file.

Even so, with problems that frequently, I suspect you have some network hardware
issues or some people who are whacking their reset button while the file is open.
 
Basically, this is a new database. I've been under the
gun trying to get it done quickly. I was thinking of
going to front-end back-end, and I'm defineately going to
now. Thanks!
 
Greg Hill said:
Basically, this is a new database. I've been under the
gun trying to get it done quickly. I was thinking of
going to front-end back-end, and I'm defineately going to
now. Thanks!
Click to expand...

Just as an FYI. I always felt this was a "Best Practice", but wondered about what
the *real* odds were on the file getting corrupted. My experience has shown that it
falls into the same category as making backups for Access 97. You know you should do
it, but you might go months or years without getting burned. In Access 2000 however,
my experience suggests that it's an absolute necessity.

I've got an A97 app that a whole department (about a dozen people) share the "wrong
way" (their decision). It has gotten corrupted about three times in five years. I
threw together a small, simple, A2K contacts database recently which had a single
person using it. A few days after it was on line they said they wanted a second
person to help with the initial data entry. No big deal I thought. I just created a
shortcut for the second person. I had to fix that file about five or six times the
first week before I finally went ahead and split it. Nary a problem since.
 
Rick Brandt said:
Just as an FYI. I always felt this was a "Best Practice", but wondered about what
the *real* odds were on the file getting corrupted. My experience has shown that it
falls into the same category as making backups for Access 97. You know you should do
it, but you might go months or years without getting burned. In Access 2000 however,
my experience suggests that it's an absolute necessity.

I've got an A97 app that a whole department (about a dozen people) share the "wrong
way" (their decision). It has gotten corrupted about three times in five years. I
threw together a small, simple, A2K contacts database recently which had a single
person using it. A few days after it was on line they said they wanted a second
person to help with the initial data entry. No big deal I thought. I just created a
shortcut for the second person. I had to fix that file about five or six times the
first week before I finally went ahead and split it. Nary a problem since.
Click to expand...

A97 was reasonably fine with this but A2000 wasn't. Agreed. That
seems to be what I've seen in the newsgroups too.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top