ldb and db corrupt

[Annette Massie]

I have an 2000 database that is getting corrupt many times a day. The
application is sittin on a network with about 5 users accessing it.
Most times I get a call with the user saying the application needs to
be repaired. I repaire the db and 8/10 times it will repair. Lately
after the repair, I have found 1-2 forms not usable. The past dozen
times I have had to create a new db, import all objects except for two
forms and then import them from an older version. Then all is well.

Is there something in those forms that is causing a corruption?

I have also been watching the .ldb files. 9 out of 10 times when no on
is in the db, the .ldb is still out there. I access the application
and immediately exit it and the .ldb goes away.

Is there a reason why the .ldb is not deleting when the last user is
out? Is this a permissions thing?

I don't think people are trashing out of the db the wrong way
(control/alt/delete) or just shutting down, however I am at a lost why
this application is getting corrupt so much with so few users.

This app has run well for more than a few years and within the last 3
months is just going to pot. I have no idea where to begin looking. I
am concerned with the .ldb's not being deleted and the 1-2 forms
usually with problems.

Your help or pointers would be GREATLY appreciated.

Thanks!

[Scott McDaniel]

Corrupt Access files are often caused by flaky network connections. Does one
user consistently have more trouble than others? If so, look at the network
hardware for that user. If all users have trouble, look at the "server", the
machine housing your data tables. Check Tony Toews site for info on other
situations and fixes:

http://www.granite.ab.ca/access/corruptmdbs.htm

--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP

"Smash forehead on keyboard to continue ... "
"Annette Massie" <an******@co.sa int-croix.wi.us> wrote in message
news:c6******** *************** ***@posting.goo gle.com...

I have an 2000 database that is getting corrupt many times a day. The
application is sittin on a network with about 5 users accessing it.
Most times I get a call with the user saying the application needs to
be repaired. I repaire the db and 8/10 times it will repair. Lately
after the repair, I have found 1-2 forms not usable. The past dozen
times I have had to create a new db, import all objects except for two
forms and then import them from an older version. Then all is well.

Is there something in those forms that is causing a corruption?

I have also been watching the .ldb files. 9 out of 10 times when no on
is in the db, the .ldb is still out there. I access the application
and immediately exit it and the .ldb goes away.

Is there a reason why the .ldb is not deleting when the last user is
out? Is this a permissions thing?

I don't think people are trashing out of the db the wrong way
(control/alt/delete) or just shutting down, however I am at a lost why
this application is getting corrupt so much with so few users.

This app has run well for more than a few years and within the last 3
months is just going to pot. I have no idea where to begin looking. I
am concerned with the .ldb's not being deleted and the 1-2 forms
usually with problems.

Your help or pointers would be GREATLY appreciated.

Thanks!

[Tony Toews]

an******@co.sai nt-croix.wi.us (Annette Massie) wrote:

I have an 2000 database that is getting corrupt many times a day. The
application is sittin on a network with about 5 users accessing it.
Most times I get a call with the user saying the application needs to
be repaired. I repaire the db and 8/10 times it will repair. Lately
after the repair, I have found 1-2 forms not usable. The past dozen
times I have had to create a new db, import all objects except for two
forms and then import them from an older version. Then all is well.

Is there something in those forms that is causing a corruption?
Possibly. The very first thing you should do though is to split your app.

You want to split the MDB into a front end containing the queries, forms, reports,
macros and modules with just the tables and relationships. The FE is copied to each
network users computer. The FE MDB is linked to the tables in the back end MDB
which resides on a server. You make updates to the FE MDB and distribute them to
the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page at
http://www.granite.ab.ca/access/splitapp/ for more info. See the Auto FE Updater
downloads page http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. It also supports Terminal Server/Citrix quite nicely.
This app has run well for more than a few years and within the last 3
months is just going to pot. I have no idea where to begin looking.

I suspect the problem started with a new server or Service Pack on the server.

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]

"Scott McDaniel" <sc***@no.spam. thedatabaseplac e.net> wrote in
news:R-*************** *****@comcast.c om:

Corrupt Access files are often caused by flaky network
connections.

For what it's worth, I've never encountered a single corrupt MDB
that was caused by bad hardware. In my experience, it's always
software (though I'm counting NIC drivers as software).

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

[Tony Toews]

"David W. Fenton" <dX********@bwa y.net.invalid> wrote:

Corrupt Access files are often caused by flaky network
connections.

For what it's worth, I've never encountered a single corrupt MDB
that was caused by bad hardware. In my experience, it's always
software (though I'm counting NIC drivers as software).

I've seen corruptions in an office in an old house which had very flaky power.
While all the workstations were on UPSs, which beeped several times in the hour I was
there, the hub was not on a UPS.

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

[Thilo Immel]

David,

Corrupt Access files are often caused by flaky network
connections.

For what it's worth, I've never encountered a single corrupt MDB
that was caused by bad hardware. In my experience, it's always
software (though I'm counting NIC drivers as software).

On site Goettingen we have seen this.

The customer told me: "No, the server NIC could not be the reason,
it's a 3-... card". So we checked all the workstations first.

But last, it was the high priced network card at the server.

But mostly the problems are caused by the poor low priced cards (or
thier drivers, ok).

Regards

Thilo Immel
Access Rescue Service www.atroplan.com
Access Memory Reporter 1.0 available now.
A tool that reports the amount of memory each table and each index
needs in a MDB file.

[Thilo Immel]

David,

Corrupt Access files are often caused by flaky network
connections.

For what it's worth, I've never encountered a single corrupt MDB
that was caused by bad hardware. In my experience, it's always
software (though I'm counting NIC drivers as software).

On site Goettingen we have seen this.

The customer told me: "No, the server NIC could not be the reason,
it's a 3-... card". So we checked all the workstations first.

But last, it was the high priced network card at the server.

But mostly the problems are caused by the poor low priced cards (or
thier drivers, ok).

Regards

Thilo Immel
Access Rescue Service www.atroplan.com
Access Memory Reporter 1.0 available now.
A tool that reports the amount of memory each table and each index
needs in a MDB file.