Glad to hear you worked through this. Sometimes there is no explaining what
goes on. As you noted, however, a backup strategy is always a good idea:

Make backups. Keep multiple generations of backup. Periodically test you
backups to prove they really are. Don't depend on just one media type for
your backups. Don't keep all of your backups in one place or on one machine.

Thanks for the feedback.

<anonymous[at]discussions.microsoft.com> wrote in message
news:1a5c301c44e9a$03b43b90$a301280a[at]phx.gbl...
- quote -

In microsoft.public.money, <anonymous[at]discussions.microsoft.comwrote:

- quote -

In Tools-> Options-> Backup 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 suggest use of a USB Flash drive also. They typically act like a
big floppy.

* This has two advantages. You can change the file name
occasionally. I like to pick a name something like money040608.
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.

- quote -

Did read it, tried re-registering the xml dll and dumping
the browser cache, no effect.

So as a shot in the dark, I tried one more attempt before
going to a clean start via export/import using msmoney -s
(had to be the fifth time I tried it) and everything
started working again. Not sure why, but all looks good
now and I am currently re-evaluating my back strategy,
keeping more than one generation for instance!

Thanks for the help.
Ken

Have you read http://umpmfaq.info/faqdb.php?q=104?

"Ken Kerr" <anonymous[at]discussions.microsoft.com> wrote in message
news:19ef801c44dc0$10c48270$a501280a[at]phx.gbl...
- quote -

- quote -

Hadn't thought of that.

The transaction report does show all expected data for
both affected accounts, so it's obvious that the data is
there, I just can't get into the register for the
accounts.

Perhaps just the links are broken to the register, but if
so, how to fix them?

Ken

What if you try to, say, create a transaction report for these accounts?

You may need to read http://umpmfaq.info/faqdb.php?q=104.
http://umpmfaq.info/faqdb.php?q=130 might also apply.

<anonymous[at]discussions.microsoft.com> wrote in message
news:18ecd01c44c88$9775a7b0$a301280a[at]phx.gbl...
- quote -

- quote -

When I click on the link for the account in the home page
or the accounts list screen, nothing happens at all. No
error, no hourglass, nothing. It just doesn't go anywhere.

All other accounts operate normally except for thest two.

Ken,

I would suggest restoring from the most recent backup you have prior
to sync with MSN.

Then, if you want to try reconcile and sync again you may want to
first turn of syncing with MSN to clear your online data, reconcile
the accounts, and then start clean with MSN.

Personally, I abandoned MSN sync a few years back. There were just
too many issues related to local file corruption.

Good Luck!

Regards,
John Buschman



"Ken Kerr" <kkerr[at]kerrkj.dsl.telerama.com> wrote in message news:<18e1e01c44bea$d97bdba0$a101280a[at]phx.gbl> ...
- quote -

What happens when you "can't open" them?!?

"Ken Kerr" <kkerr[at]kerrkj.dsl.telerama.com> wrote in message
news:18e1e01c44bea$d97bdba0$a101280a[at]phx.gbl...
- quote -

I have two active accounts in the money file that I am
unable to open the register. Other accounts in the file
operating fine.

This started after reconciling these accounts last
evening, then synching with MSN money. The properties for
the affected accounts can be edited from the account list
screen, but the register for the affected accounts cannot
be opened via any method I can find.

I have tried both the "Quick repair" from the file menu,
and the salvage utility, but no change in the issue.

Ideas?

Ken Kerr