Constantly corrupting Access 2002 database

[heather e blair]

We have an Access 2002 database of about 35 M with about 7 users. The data
lives on the server (Windows 2000 server), while the queries, forms, reports,
etc. live in a file that is on each person's C drive. There is also a
workgroup file to set the permissions for various groups.

Everybody is running Windows 2000 on their local computer.

People start using the database about 7:30 or 8 in the morning, and then
around noon, one by one they can no longer connect. When I try to open it
I get the error that it is an unrecognizable file or corrupt. If I open it
exclusively, I can rebuild it OK.

What could be causing this? Nobody is exiting their database improperly,
and it worked just fine for months and months until this week!

I even created a new data file and imported the existing tables into it,
but the same error happened.

Another smaller split database with three users has been acting the same way.
Could it be our network connections? How would I troubleshoot and fix this
problem.

- H

--
"Verbosity leads to unclear, inarticulate things." -- Vice President
Dan Quayle, 11/30/88

[Tony Toews]

Re: Constantly corrupting Access 2002 database

h431@midway.uch icago.edu (heather e blair) wrote:
[color=blue]
>We have an Access 2002 database of about 35 M with about 7 users. The data
>lives on the server (Windows 2000 server), while the queries, forms, reports,
>etc. live in a file that is on each person's C drive. There is also a
>workgroup file to set the permissions for various groups.[/color]

Good, glad to see things are split.
[color=blue]
>People start using the database about 7:30 or 8 in the morning, and then
>around noon, one by one they can no longer connect. When I try to open it
>I get the error that it is an unrecognizable file or corrupt. If I open it
>exclusively, I can rebuild it OK.
>
>What could be causing this? Nobody is exiting their database improperly,
>and it worked just fine for months and months until this week!
>
>I even created a new data file and imported the existing tables into it,
>but the same error happened.
>
>Another smaller split database with three users has been acting the same way.
>Could it be our network connections? How would I troubleshoot and fix this
>problem.[/color]

It could be a lot of things. Has anything changed? Are there new set of patches on
the server? Some new hardware somewhere? A new client PC?

The next thing to check is the OpLocks setting on the server.

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
--
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

[David W. Fenton]

Re: Constantly corrupting Access 2002 database

h431@midway.uch icago.edu (heather e blair) wrote in
news:qjwlc.19$2 5.3818@news.uch icago.edu:
[color=blue]
> What could be causing this? Nobody is exiting their database
> improperly, and it worked just fine for months and months until
> this week![/color]

Check that all users' installations of Access are at SR1a or later
and that Jet 4 is at service pack 6 or later. If even one user is
not up-to-date on both of these (not one, but both), it can lead to
corruption.

Once you've got everyone on a stable version of Access (which the
original release of A2K and all versions of Jet 4 before SP6 are
not), then you should start looking at other issues.

It's the first thing I alway check when a client experiences
corruption, and it's almost always because a clean workstation has
somehow been reverted to an earlier version (something got
re-installed, or the workstation was rebuilt or replaced or
whatever).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Tom van Stiphout]

Re: Constantly corrupting Access 2002 database

On Tue, 04 May 2004 03:31:14 GMT, "David W. Fenton"
<dXXXfenton@bwa y.net.invalid> wrote:

Everything David said. And you need to write some code that at
startup time checks for these things, and presents an error message to
the user ("the minimum version x of Office was not found" or "the
minimum version y of Jet was not found") and quits, and/or sends an
email to the administrator.

-Tom.

[color=blue]
>h431@midway.uc hicago.edu (heather e blair) wrote in
>news:qjwlc.19$ 25.3818@news.uc hicago.edu:
>[color=green]
>> What could be causing this? Nobody is exiting their database
>> improperly, and it worked just fine for months and months until
>> this week![/color]
>
>Check that all users' installations of Access are at SR1a or later
>and that Jet 4 is at service pack 6 or later. If even one user is
>not up-to-date on both of these (not one, but both), it can lead to
>corruption.
>
>Once you've got everyone on a stable version of Access (which the
>original release of A2K and all versions of Jet 4 before SP6 are
>not), then you should start looking at other issues.
>
>It's the first thing I alway check when a client experiences
>corruption, and it's almost always because a clean workstation has
>somehow been reverted to an earlier version (something got
>re-installed, or the workstation was rebuilt or replaced or
>whatever).[/color]