Repairs caused by multiple users

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Phlip - 18 Jun 2005 07:37 GMT

I have a database that is used in around 50 organisations on small networks
of up to 10 users. I have been experiencing problems at several sites who use
various Access versions from 2000 up.. Sometimes several times a day for no
apparent reason when someone new tries to open the database they get the
message that the database needs repairing, even though the other users are
working Ok. All of these sites have or have had Windows 2000 workstations at
one time or another (some have upgraded to XP). I have a suspision that the
Windows 2000 has had something to do with the problem but have not been able
to pin it down. Access 97 sites never have these problems
Anyone got any suggestions.
Thanks

Signature

PhlipC

Reply to this Message

Brendan Reynolds - 19 Jun 2005 13:20 GMT

Sounds like the 'oplocks' problem. That problem and its solution, along with
other possible causes and solutions, are described in the following KB
article ...

http://support.microsoft.com/default.aspx?scid=kb;en-us;300216

Signature

Brendan Reynolds (MVP)

>I have a database that is used in around 50 organisations on small networks
> of up to 10 users. I have been experiencing problems at several sites who
[quoted text clipped - 12 lines]
> Anyone got any suggestions.
> Thanks

Reply to this Message

Tony Toews - 24 Jun 2005 03:53 GMT

>I have a database that is used in around 50 organisations on small networks
>of up to 10 users. I have been experiencing problems at several sites who use
>various Access versions from 2000 up.. Sometimes several times a day for no
>apparent reason when someone new tries to open the database they get the
>message that the database needs repairing, even though the other users are
>working Ok.

Just to follow up on Brendan's posting. And I agree with him that the
problem is very likely to be OpLocks.

This behaviour is typical. When Access is doing an update it sets a
corrupt flag in the mdb momentarily. If the update is interrupted
then this corrupt flag is set. But Access only checks the existence
of this flag when it opens the database for the first time. Thus
other users will happily work away for hours without realizing there
is a problem. While users attempting to open the MDB get the
repairing message.

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony

Signature

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

Reply to this Message