Many corruption cases only manifest themselves in very limited ways--certain
reports, say. For this reason, you raise an entirely valid point: if you
don't have good backup depth, you can have a corruption episode go unnoticed
longer than your backup depth.

Of course, if you are rolling back to a backup six months old, you will have
six months of transactions to make up as well. There is no good solution to
this.

But, again, it does not appear to be a unique function of file size. You
could have a file seven months old that's been carrying a problem for six
months just as easily as a file that's got 12 years of data in it carrying
six month old corruption.

"Jeff" <jeff[at]phony.com> wrote in message
news:e%23WS7YRDFHA.3688[at]TK2MSFTNGP14.phx.gbl...
- quote -

- quote -

I agree and backup regularly. But that only helps if you discover the
corruption before you have backed up several generations of the corrupted
file. If the file becomes corrupted in some way does it immediately
manifest itself or can it remain silent if you are not accessing that part
of the data?

--

Jeff Stevens
Email address deliberately false to avoid spam
jeff[at]stevens.com


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:eY3rNAIDFHA.3376[at]TK2MSFTNGP12.phx.gbl...
- quote -

- quote -

What tends to cause corruption, how does it manifest itself, and how can one
minimize the risk?

Thanks.

--

Jeff Stevens
Email address deliberately false to avoid spam
jeff[at]stevens.com


"Cal Learner-- MVP" <via_newsgroup[at]please.tnx> wrote in message
news:81lc01p081q2j80gl94tmt0ees01o5kva7[at]4ax.com...
- quote -

Time and use and strange things that cause corruption are more likely to
occur over a long time. Data files grow large over that long time. But large
files don't seem to have corruption problems just because of size.

The BEST insurance against corruption problems is a good backup strategy:
have multiple generations of backup on multiple media types and test them
occasionally to confirm they really are backups. This not only can save you
from file corruption problems but from dead hard disks and stolen computers
and so forth.

"John Smith" <3rtwemte001[at]sneakemail.com> wrote in message
news:cmkc01p0c1g173e8mi5jut69rfj2en2fgq[at]4ax.com...
- quote -

In microsoft.public.money, John Smith wrote:

- quote -

Should not be a problem. If you want the growth of your file to
slow, you can reduce the number of quotes that you fetch.

- quote -

Corruption is to be feared, but not because of size.

In Tools-> Options-> Backup [M05: Tools-> Settings-> BackupOptions]
I suggest checking
x Automatically backup to hard disk on exit
x Prompt me before backing up each time*
x Make my file small ...

Then periodically, perhaps once per month or more, copy your
latest backup (named differently from your earlier backups) to a
CDR. With XP, this can be a copy and paste operation. Otherwise
use the burning software that came with your CDR drive.

I strongly suggest use of a USB Flash drive also, in addition to
backing up to your hard drive. They typically act like a big
floppy. For a more automated way to make multiple backups, see
Glyn Simpson's method at http://money.mvps.org/backup.aspx


* This has two advantages. You can change the file name
occasionally. I like to pick a name something like money050111.
Then it is easy to change the name to have multiple backups. The
..mbf extension is automatic. The other advantage is that you can
choose "Don't Back Up, or you change your mind about exiting by
simply clicking the X in the upper right of the pop-up box.

I have been using Money for the past four years, and over this time my
Money file has grown to a fairly large size. I was wondering if this
can cause any problems later on.

I started with 2001 then upgraded to 2003 and now am using 2005. I
would hate for the file to get corrupted, as I have 4 years of data
stored in it. Is this an unfounded fear?


Thanks!