Compact and Repair Database?

[Logo]

My "IT Guy" says he would never use compact and repair on a database but
wouldn't elaborate. Are there any arguments to support his reasoning? TIA

 

[roccogrand]

Logo,

I run Compact & Repair in auto mode and have never had a problem. I don't
worry about trashing my databases with a C&R operation because I back them up
regularly. But when A2007 was first released, there were alleged incidences
of auto C&R destroying folks' databases.

I strongly recommend backing up your databases before doing any operation.
You should also save your database after adding critical data. For one of my
databases I am up to version 56 and I have several backups on the internal
drive, on external drives, in the cloud, and even DVDs. It is better to be
safe than sorry.

David

 

[Jerry Whittle]

I recommend to NOT use the Compact on Close option. No need to do it that
often.

I recommend C&R manually when something seems strange. Before doing that,
make a complete backup first. It's possible for a C&R to fail and ruin a
database.

There's a better way to C&R a database. Download the JetComp tool from MS.
It does a better job of fixing problems plus forces you t make a backup.

 

[kc-mass]

This question should really go to David Fenton who has very strong opinions
on access compact and repair.

Essentially don't do it.

Regards

Kevin

 

[Dirk Goldgar]

This question should really go to David Fenton who has very strong
opinions on access compact and repair.

Essentially don't do it.

I disagree. There are times when a Jet/ACE database needs to be compacted.
Now, many people feel that setting the Compact On Close option is a bad
idea, and they have a valid point. I wouldn't want to compact a database
"into itself" without first ensuring I have a good backup.