[moneydance] data file corruption

[Bradley Pursley]

I've had something similar happen but for me it happened while I was
only entering transactions in my checking account.  The original file
was corrupted and the backup file was missing a lot of information.  I
had to go to a much older backup file (I have MD make a new one each
day) and re-enter all of the transactions that it didn't have.  Yeah, MD
seems to have this tendency to corrupt it's working files, especially
when it crashes.  I am thinking that what needs to be changed in it's
code to protect the main data file is what many programs do.  Which is
to immediately make a working backup of the data file and only work with
the backup.  When the programs saves it's contents, to rename the
original data file to a backup file and save a new main file.

Gordon Alley wrote:
> I just wanted to relate this incident to the list in case it's not just me.
>
> I'm using Moneydance 2007 build 566 on an iMac G4 800 with 1GB RAM and
> 6.5 GB of free space on my 60 GB internal drive.
>
> I had entered a few credit card transactions. Then I added a 19
> securty SELL transactions that I had made earlier in the day. I had 4
> BUY transactions to add for new securities. I used the Add Security
> button to add the 4 new securities. But the Add Security dialog did
> not go away after the last security was added. After clicking around
> trying to get some response from MD, eventually I got the spinning
> beach ball indicating that MD had stopped responding. I had to Force
> Quit MD.
>
> After returning to the Finder, I discovered that the Dock seemed to
> have quit (I have it set to auto-hide, and it wouldn't un-hide). I
> logged out and back in to get things back to normal again.
>
> When I tried to open my MD file, MD asked me if I'd like to open the
> more-recent backup file, and I told it to do so. But, to my chagrin,
> after a short delay I was presented with an alert that said "Error:
> Cannot read file: java.io.EOFException". Also, when I look at the
> files, the backup is about half the size of yesterday's file. Doesn't
> look good!
>
> So I guess I'm going to have to re-enter all those transactions again. Arghhh!
>
> I think I'll reboot and run Applejack to let it check out the disk
> before continuing, though.
>
>