Agreed. My understanding is that when a bill is deleted or added then a new
schema is created which contains all previous and current bills. So if you
have been using Money for many years it has to follow a trail through all
the schemas ever created.

I can see that given enough time/bill changes one might have to repeat the
exercise and Nuke them again.

Hopefully by that time MS will have developed a utility to do it for us!

--
Regards
Bob Peel,
Microsoft MVP - Money

For UK tips & fixes see
http://support.microsoft.com/default...d=fh;EN-GB;mny.


I do not respond to any emails that I have not specifically asked for.

"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:%23qzRn97SIHA.1208[at]TK2MSFTNGP03.phx.gbl...
- quote -

And a lot more besides or it wouldn't be there. Just removing (select then
Delete, one at a time) the scheduled items from the UI does NOT do all that
Nuke does.

"Bob Peel, MVP" <bob_peel[at]kiandra.freeserve.co.uk.INVALID> wrote in message
news:ufRxuovSIHA.1208[at]TK2MSFTNGP05.phx.gbl...
- quote -

I think the umpmfaq entry has copious warnings. YMMV.

"John Miller" <John.L.Miller[at]no-spam.verizon.net> wrote in message
news:OdYsXnvSIHA.5128[at]TK2MSFTNGP05.phx.gbl...
- quote -

See http://money.mvps.org/faq/article/418.aspx

It literally removes ALL bills and deposits. So as per the above you need a
record of forthcoming bills & deposits.

Some people have suggested having a second PC with the original file
alongside whilst you rebuild the bills & deposits data.

--
Regards
Bob Peel,
Microsoft MVP - Money

For UK tips & fixes see
http://support.microsoft.com/default...d=fh;EN-GB;mny.


I do not respond to any emails that I have not specifically asked for.

"John Miller" <John.L.Miller[at]no-spam.verizon.net> wrote in message
news:ecdEnRvSIHA.5360[at]TK2MSFTNGP03.phx.gbl...
- quote -

Yeah - I'm 'bout wired like a fiddle string.

- John

Oops - never mind, Kevin. I just stumbled upon a link to
http://umpmfaq.info/faqdb.php?q=187 in another post. Reading the referenced
article leaves me with two observations:

1. Microsoft has obviously recognized serious internal disarray in Money.
How unconscionable that they would "fix" the problem by unleashing such a
complex capability with potentionally disastrous results on their users.
Using the "Nuke the Bills" feature makes fiddling with RegEdit look like
child's play: at least, you can back up and restore the Registry to its
previous state in a single operation.

2. Why on earth would any member of this newsgroup - particularly seasoned,
active contributors - point users in the direction of this option without a
blatant warning and disclaimer attached?

Caveat emptor, eh?

- John

Kevin -

Thanks for the advice. I'll give it a shot.

Just what data is removed by the "Remove all Bills data" repair process
option you mentioned? Anything that I'd miss?

- John

John Miller,

I'm assuming that M2008 incorporates the "File > Repair Money File > Remove
all Bills data" option
that M2007 has.
Using this "feature" has GREATLY improved start-up time as well as all
around performance.
Maybe you should try a trial version.

-Kevin

Sounds like you've already had your morning coffee to me.

I've used MS$ for 10 years, give or take, upgrading to a new version every
2-3 years. In general, my experience is the same: one or two features that
I use and appreciate; a slew of new stuff that is of no use to me and serves
to further bloat the application's resource-hogging behavior; and
occasionally, a bug fix. I would purchase MS$ 2008 (basic, H&B, or
whatever) in a heartbeat if it included some serious performance
optimization (faster startup, quicker response time), but I fear that, as in
days past, I'm dreaming. Reviewing the "what's new" info on Money's home
page, the only thing that I see that would be of any benefit to me is the
ability to link to related files (like receipts and check images), but that,
coupled with all the other glitz and twinkle, makes me suspect that the
latest version will start slower, respond more sluggishly, and gobble more
memory and CPU time than its hungriest predecessors.

I'd appreciate any experiential feedback, and would be delighted to be
proven wrong in my cynicism.

Thanks in advance.

- John