I think Microsoft gave us 'Remove all bills' because it was easier than
repairing the repair function.
--
Chris Cowles
Gainesville, FL

"JohnA" <John[at]TheAtas.org-spamguard> wrote in message
news:e3j9Yx6%23GHA.1220[at]TK2MSFTNGP04.phx.gbl...
- quote -

I have around 45 bills... took about 3-4 minutes to "Change"... after doing
the "Remove all bills data" and adding them back in manually, each "Change"
takes approximately 8 seconds. I also noticed that the Report on Bills
listed them differently - before nuking the bills, each bill would list any
details on top of the corresponding multi-category transaction; after nuking
the bills, the details follow the transaction as expected. Anyway, it seems
to be worth the time to do this but I still don't know why the repair
function couldn't have fixed it.

-- John

"johndog" <johndog[at]discussions.microsoft.com> wrote in message
news:9FF015F3-3828-4678-977B-4AC66C4A4C18[at]microsoft.com...
- quote -

Yes, the "Remove all Bills data" has improved my performance also. It has
eliminated any lockups so far, which has been nice.

Is there any way that this could be due to importing previous Money
versions' data files? I also toyed with the idea of starting a new Money
2007 file from scratch to test and see if it still has the problem, but the
above method worked. Please post if you do try a new Money file. I
currently don't have any Bills for items that would show up in accounts (only
bills and transfers)

Rgds,
Andy

"johndog" wrote:

- quote -

Chipping in, I had performance problems with Money myself. Money didn't
freeze on me to the extent that I had to kill it with Task Manager, but it
was ridiculously slow when trying to perform transaction matches. For
instance, when I clicked the 'Change' button on a [un]matched transaction, it
would take 8-10s to process before finally giving me the option to manually
match the transaction.

As recommended by Carl, I tried 'Remove all bills data' on a scratch copy of
my money data file, and SNAP! Now it's instantaneous!

I now wonder if the bills data was also responsible for my frequent need to
'Quick Repair' the file. Why isn't there a KB on this?


"Cal Learner-- MVP" wrote:

- quote -

So, I tried remove all bill data. Still having the same problem when trying
to unmatch transactions. Is Microsoft going to fix this bug in a later
update? It looks to be a problem for many people.
Thanks,
Amy

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

- quote -

Perhaps I'm misunderstood here. It's not that things are slow: they're
not. It's that Money has hung with 100% CPU use. It's a totally
different thing.

I've actually moved the file to a number of different computers with no
change in behavior as well.

- quote -

Yeah, it's retail. Money support hasn't been helpful in the past, but
off I go. Thanks.

In microsoft.public.money, dnanian wrote:

- quote -

So you have removed bills data with the Money 2007 tool.
You have done Quick and both Standard repairs.
You have removed Passport/LiveID (just a wild hunch)
You have archived (which does not normally speed things up).
Disconnecting from the internet does not speed things up.
You've tried (seriously) clean installing XP and only putting Money
on there (after security updates have been applied) with no change.

I would try a new file on that same computer, and restoring your
slow file via a USB flash drive to a different computer temporarily.

I would also suggest contacting Microsoft support, if you are
running a retail (not trial or OEM) install.

Cal Learner-- MVP wrote:
- quote -

At this point, I've removed the ID, made sure updates were disabled
(they were), and disabled my network connection.

No difference. 100% CPU use by Money and dead in the water when doing
this simple operation.

Cal Learner-- MVP wrote:
- quote -

That would be strange, since I've never had any data synchronized or
uploaded to MS's servers, but I'll try it. Regardless, I've never had
updates from MSN Money (other than stock price stuff).

I have tried running logged in and not, and online and not, with no
difference.

- quote -

Indeed, I have done that. I've also attempted archiving a huge amount
of data. Neither matters: exactly the same thing happens.

In microsoft.public.money, dnanian wrote:

- quote -

I would consider removing Windows LiveID/Passport on a *copy* of
the file to see if that affects the speed problem. That might
require you to clear
Tools-> Settings-> ReceiveAccountUpdatesFromMSNMoneyMyAccounts.
Another thing to try is to disconnect your network connection to
see if that impacts things. I don't have specific problem in mind,
but I am wondering if something is trying to happen online.

You might also try both level 1 and level 2 on the Standard repair.

Cal Learner-- MVP wrote:
- quote -

Sorry, Cal, You must have missed where I indicated that I had already
done that.

- quote -

Yes, I do.

In microsoft.public.money, dnanian[at]gmail.com wrote:

- quote -

Consider trying File-> Repair-> RemoveBillsData on a copy of your
file.

Do you have a Windows LiveID/Passport on the file?

Hi, Cal -- I'm also having this problem. I've already removed Bills
data, and it doesn't seem to have anything to do with it. As others
have indicated, I've done both a quick and standard repair (the Quick
is obviously pointless, since it gets done when you restart Money after
the forced quit anyway).

I don't just have this happen when matching transactions, though. At
present, I'm simply trying to reconcile a statement, and I get the hang
either immediately on entry to the register after entering the initial
figures, or when I change the status of the first transaction.

When this happens, my CPU goes to 100% (all Money, according to Task
Manager) and I can't do anything. I've left it for hours in this state
to see if it would ever recover, and it does not.

I've had this happen during virtually any operation that involves
transactions -- matching, reconciling, entering -- even printing checks
(after, when it updates the check #s).

I've tried (seriously) clean installing XP and only putting Money on
there (after security updates have been applied) with no change. This
is most definitely a Money issue.

Kevin wrote:
- quote -

That did not work. In addition, I do not believe this is connected to bills
per se. This happens with any transaction that Money so happens to match.

"Cal Learner-- MVP" wrote:

- quote -

In microsoft.public.money, Hart wrote:

- quote -

I don't know. Try that action on a copy of your file to find out.

I am also having to use task manager to shut down money when trying to
unmatch transactions downloaded from my bank. Money is not necessarily
trying to match it to bills coming due, just other transactions I have put
into the register. Will this repair of removing all bill data really help
in this instance?
Amy

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

In microsoft.public.money, EricA wrote:

- quote -

Consider trying File-> Repair-> RemoveAllBillsData on a copy of your
file. This Remove All Bills Data feature would be for people who
have experienced their Money file to run excessively slow.

To get some information within the program,
File-> Repair-> RemoveAllBillsData
Read the information. Then click cancel.

Before proceeding, make an extra copy or backup of your file
in case you want to undo something.

The problem will be that if you remove all bills, you will probably
want to add at least some of your bills back. This can be done
manually with the aid of the reports that you print out before
removing the bills.

A technique that could help simplify re-entering your bills
afterward would be to go your register and selecting a
representative instance of your past bill and selecting "Make
Recurring" (Ctrl+E). This would be especially helpful if the bill
is complex, such as involving a split.



- quote -

I'm also having the problem. The program hangs consistently when
trying to unmatch a transaction. I even did a fresh install of WinXP,
and that didn't solve the problem.

Kevin wrote:
- quote -

I'm having the same problem when I attempt to unmatch a transaction. I have
given Money close to an hour once to return to normal.

"JohnA" wrote:

- quote -

How long are you waiting before deciding that it is hung... Money "thinks"
for a long time depending on your Money file (at least 2 minutes for me) but
it finally will return.

-- John

"Ray Garrett" <RayGarrett[at]discussions.microsoft.com> wrote in message
news:3D62B29C-F239-4E8E-B695-B6DACA730480[at]microsoft.com...
- quote -