Prevent DB from corrupting

[Anthony]

What steps can I take to prevent a database from becoming corrupted?

ty

 

[Albert D. Kallal]

What steps can I take to prevent a database from becoming corrupted?

I don't tell you how to prevent corruption, but I do with some nice pictures
(and diagrams) explain WHY a corruption can occur on a bad network
connection

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

at least, after you read the above you gain an idea as to why curruption can
occur....

 

[Allen Browne]

See:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

 

[Joseph Meehan]

What steps can I take to prevent a database from becoming corrupted?

ty

Have you had or are you having problems?

Always backup. No matter what, corruption can happen to any file on any
computer.

Of course follow the links others have provided, even if you have good
backups. You don't want any corruptions.

 

[David W. Fenton]

Have you had or are you having problems?

Always backup. No matter what, corruption can happen to any
file on any
computer.

But it hardly ever does in a properly functioning environment. That
means no wireless, decent hardware and switches, well-managed
servers and the correct software patches on all the workstations.

This should be pretty basic, however annoying it is to troubleshoot
it.

I know the knee-jerk reaction of most in these forums is that
corruption comes from bad hardware, but in my experience it's almost
always been software, especially since the introduction of Jet 4,
and the key cause with the few clients of mine who've had it has
been reversion of workstation Access software installations to the
release version of Access, without the Access/Office service packs
and the latest Jet service packs (though this latter is more likely
an issue with reverting the OS, as Jet is an OS component that is
patched in the OS service packs).

 

[Joseph Meehan]

But it hardly ever does in a properly functioning environment. That
means no wireless, decent hardware and switches, well-managed
servers and the correct software patches on all the workstations.

True, but if you work with critical data, then you back up.

 

[David W. Fenton]

True, but if you work with critical data, then you back up.

I wasn't suggesting no backups, just clarifying the usual reason for
"corruptions." And, of course, 90% of compacts to fix corruption are
actually just resetting the flags in the MDB that marked it as
suspect (because it lacked an orderly shutdown, not because there
was actually any corruption within the data structures inside it).