Access 2000 needs to be repaired EVERY day

[Jamie]

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....

[ManningFan]

Are you pushing the maximum size (2GB)? We had a database that did the
same thing, had to be compacted 2x daily, and it was because it was
just short of 2GB.

When your DB failed, you should have imported the tables into an empty
database and then added the forms/reports/queries from a backup, you
wouldn't have lost anything.

Jamie wrote:

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....

[Allen Browne]

Jamie, there is a problem here that needs fixing.

Starting point would be to ensure the repairs are complete. Name AutoCorrect
must be off in both the back end and the front ends. Decompile. And probably
import everything into a new database, as per first symptom in this article:
http://allenbrowne.com/ser-47.html

Secondly, verify that each user has a separate copy of the front end (i.e.
they are not actually using the same mdb front end.)

Next, check out the rather lengthy list in:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html
right through to ensuring everyone is using an MDE.

If you are still stuck after that, log your users in and out so you can
identify which computer/user/network connection is falling off and
corrupting the data.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jamie" <it*********@cox.netwrote in message
news:Xn**********************************@216.77.1 88.18...

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....

[Jamie]

"ManningFan" <ma********@gmail.comwrote in
news:11*********************@b28g2000cwb.googlegro ups.com:

Are you pushing the maximum size (2GB)? We had a database that did
the same thing, had to be compacted 2x daily, and it was because it
was just short of 2GB.

When your DB failed, you should have imported the tables into an empty
database and then added the forms/reports/queries from a backup, you
wouldn't have lost anything.

Jamie wrote:

>Greeting!

I hope someone can shine a light on a problem I am having. I have 13
users on Access 2000 running FE from various PC and the BE on a new
HP Server with Windows 2003, plenty of power and RAM. Problem is, I
started getting an error that my database was in an unrecognized
format. That has happened about 3 times, the first one made me lose
about 3 weeks worth of tickets (the DB is running a Delivery Ticket
system). Now I am getting an error that the database needs to be
repaired. I have to get everyone out and so far have been able to
compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how
to stop it? I am worried that I am gonna get caught with by data
drawers down.....

Thanks in advance for any assistance you can render....

Oh, I'm nowhere near 2GB mark, maybe something like 12MB.

I did try to import the information into a new blank database, but kept
receiving an error that the db was an unrecongized format. Compact, repair
nor convert was able to do anything. Good thought, though.

[(PeteCresswell)]

Per Allen Browne:

>Jamie, there is a problem here that needs fixing.

Starting point would be to ensure the repairs are complete. Name AutoCorrect
must be off in both the back end and the front ends. Decompile. And probably
import everything into a new database, as per first symptom in this article:
http://allenbrowne.com/ser-47.html

Secondly, verify that each user has a separate copy of the front end (i.e.
they are not actually using the same mdb front end.)

Next, check out the rather lengthy list in:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html
right through to ensuring everyone is using an MDE.

If you are still stuck after that, log your users in and out so you can
identify which computer/user/network connection is falling off and
corrupting the data.

I've been here a couple of times.

For me, the low-hanging fruit would be the file server: move the application to
a different server and cross your fingers. Dunno the exact nature of a server
problem that can cause corruptions, but I've had a couple of instances where
changing servers stopped the problem right away and permanently.

The other known corruption cause I've had was a bad NIC in one of the user's
machines.

--
PeteCresswell

[David W. Fenton]

"(PeteCresswell)" <[e-mail] in
news:05********************************@4ax.com:

For me, the low-hanging fruit would be the file server: move the
application to a different server and cross your fingers. Dunno
the exact nature of a server problem that can cause corruptions,
but I've had a couple of instances where changing servers stopped
the problem right away and permanently.

I've never seen anything like that. In my experience, the corruption
is almost always caused by software on the workstations, i.e.,
substandard versions of Access and Jet.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Allen Browne]

There was an ancient problem in Win 2000 Server, caused by a setting called
something like Opportunistic Locking (nothing to do with locking in Access),
but that was fixed yonks ago, SP2 or 3 for Win 200 Server IIRC.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"David W. Fenton" <XX*******@dfenton.com.invalidwrote in message
news:Xn**********************************@127.0.0. 1...

"(PeteCresswell)" <[e-mail] in
news:05********************************@4ax.com:

>For me, the low-hanging fruit would be the file server: move the
application to a different server and cross your fingers. Dunno
the exact nature of a server problem that can cause corruptions,
but I've had a couple of instances where changing servers stopped
the problem right away and permanently.

I've never seen anything like that. In my experience, the corruption
is almost always caused by software on the workstations, i.e.,
substandard versions of Access and Jet.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Sebastian]

Jamie a scris:

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....

I had the same problem a couple of months ago.
Five users, the database keeps corrupting every day.
The culprit was one station with Jet not being at Service Pack 8.
Updated the Jet to SP 8 and since then never got any problems.
Hope this helps.

Sebastian

[Craig Alexander Morrison]

You may want to check out your network connections.

A few years ago we had a similar problem and it was down to a faulty
connection that worked intermittently and so kept dropping the connection
and of course this can upset a Jet database.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

Small Business Solutions Provider

"Jamie" <it*********@cox.netwrote in message
news:Xn**********************************@216.77.1 88.18...

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....

[David W. Fenton]

"Allen Browne" <Al*********@SeeSig.Invalidwrote in
news:44***********************@per-qv1-newsreader-01.iinet.net.au:

There was an ancient problem in Win 2000 Server, caused by a
setting called something like Opportunistic Locking (nothing to do
with locking in Access), but that was fixed yonks ago, SP2 or 3
for Win 200 Server IIRC.

The problem was on NT 4 Server, as well.

I would try to look it up in the KB and see if changing that setting
fixed the problem, as I'm no believer in the premise that such bug
regressions never happen in code as complex as Windows.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[(PeteCresswell)]

Per Allen Browne:

>There was an ancient problem in Win 2000 Server, caused by a setting called
something like Opportunistic Locking (nothing to do with locking in Access),
but that was fixed yonks ago, SP2 or 3 for Win 200 Server IIRC.

The one I encountered was supposedly (third or fourth-hand information...)
something to do with buffer sizes.
--
PeteCresswell

[Vayse]

Have all your PCs the correct references?
I've seen an issue before one of the clients PCs was showing #Name instead
of the date. This caused several database functions to malfunction and used
to cause several tables to have problems.
Since then I always display the date on the Switchboard. Me.txtDate = Date()
That way the user will have a visual indication something is wrong, and
there is a slight chance they might actually tell you. After ignoring the
first 20 error messages of course.
Vayse
"Jamie" <it*********@cox.netwrote in message
news:Xn**********************************@216.77.1 88.18...

Greeting!

I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.

Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....

Thanks in advance for any assistance you can render....