"Linq Adams via AccessMonster.com" <u28780@uwewrote in message
news:88635c4d96834@uwe...
What you really need to understand is that C & R is one of those paradoxes
that seem to permeate Access. A function that one would think is, at least
partially, meant to decrease the chance of corruption, actually is a
frequent
cause of corruption! Because of this, C&R should never be done until a
backup
copy of the db has been made.
It's an interesting thing. I have used Access daily since I got my first
copy of V. 1.0 early in January of 1993, and I have never experienced
corruption due to Compact and/or Repair. Compact and Repair, unless you go
out of your way to force it to overwrite, reads the existing database and
creates a new one, AFAIK.
Given this and that I never had a corruption, I (almost) never make a backup
before compacting, but use the Compact-from database as my backup. On the
other hand, I backup usually every hour or so of development, so for the
databases I most work with, I have plenty of backup copies lying around.
Now, if the next time I do C&R, it corrupts the Compact-from database,
you'll hear my screams all the way to wherever you are!
Larry Linson
Microsoft Office Access MVP