TableSize & Corruption

  • Thread starter Thread starter Bob Barnes
  • Start date Start date
B

Bob Barnes

I have a Back-end Access 2000 DB with total size
around 90 Meg. That is not large.

We've had 5 Corruptions in 2 days, & Corruptions in
this DB are fairly rare.

I have a Table with 128,000 Records = not unusual, but
the design requires 87 fields. I do not like so many
fields, but the design does the job well.

Any ideas if the 129,000 Records (87 fields) might be
a factor in causing the Corruption?

TIA - Bob
 
I have a Back-end Access 2000 DB with total size
around 90 Meg. That is not large.

We've had 5 Corruptions in 2 days, & Corruptions in
this DB are fairly rare.

I have a Table with 128,000 Records = not unusual, but
the design requires 87 fields. I do not like so many
fields, but the design does the job well.

Any ideas if the 129,000 Records (87 fields) might be
a factor in causing the Corruption?
Click to expand...

I doubt that this has anything to do with the corruption. See Tony
Toews' FAQ for some ideas:

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

Two quick things to check: the two MOST common causes are a user
closing Access with ctrl-alt-del or powering down (frustrated by a
slow query perhaps); and network noise from a bad NIC.
 
John . . . Thank you.

We suspect our scenario might be a laptop hibernating.
Click to expand...

Arrggh... wouldn't have thought of it, but yes, that very well could
be the cause.
 
Back
Top