TableSize & Corruption

[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

 

[Lynn Trapp]

Is the corruption occurring in your back end or your front end? You should
take a look at Tony Toews' corruptions page:

www.granite.ab.ca/access/corruptmdbs

 

[Bob Barnes]

Back-end.

I will look at Tony's site.

Thank you, Bob

 

[John Vinson]

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?

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.

 

[Lynn Trapp]

You will want to pay particular attention to the information that Tony has
on OpsLocks. As John Vinson has also posted, the most likely cause is some
network problem or a user getting the happy finger with ctrl+alt+del

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

 

[Bob Barnes]

John . . . Thank you.

We suspect our scenario might be a laptop hibernating.

Bob

 

[Bob Barnes]

Lynn - Thank you.

-----Original Message-----
You will want to pay particular attention to the information that Tony has
on OpsLocks. As John Vinson has also posted, the most likely cause is some
network problem or a user getting the happy finger with ctrl+alt+del

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm






.

 

[Lynn Trapp]

Now that's an interesting scenario that I hadn't ever considered.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm

 

[John Vinson]

John . . . Thank you.

We suspect our scenario might be a laptop hibernating.

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