Designed that way I think. Changes to the current month in progress are only
reflected from the next one.

--
Glyn Simpson, Microsoft MVP - Money

Check http://support.microsoft.com/default...d=fh;EN-GB;mny
for UK tips and fixes for MS Money. To send Microsoft your wishes or
suggestions, use http://register.microsoft.com/mswish/suggestion.asp
or email mnyukwsh[at]microsoft.com especially if it's a UK specific wish.

I do not respond to any unsolicited email regarding Money

"Jaap" <xyz[at]nonet.com> wrote in message news:bqc69m$9n4$1[at]reader10.wxs.nl...
- quote -

- quote -

This does not happen in my version (International Standard). I noticed
however that when I change budgetamounts during the month, these changes are
not reflected in the current month. Could be designed that way though.

Any reoccuring deposits or bills cause major problems
with the budget. For the first month under BUDGETED on
the REVIEW YOUR CURRENT BUDGET STATUS screen it will list
the correct amounts of my reoccuring bills and deposits.

However, if I choose NEXT MONTH using the BUDGET PERIOD
drop-down menu and look at next month's budget Money
doubles the budgetes amount for some of my reoccuring
bills and deposits which throws next month's budget way
off.

So I called tech support and they told me that it is a
flaw with the program. They said that if I have a
reoccuring bill that is $100 Money will list it correctly
in the first months budget. However, for the second
month it will list the budgeted amount for the bill as
$200.

I have noticed something really odd. It is currently
November so if I look at November's budget it looks
fine. If I look at Decembers some of the reoccuring
bills budgeted amounts doubled, but not all of them. If
I change the date on my computer to December 1 and then
choose NEXT MONTH so that I can look at January's budget
some of the values will now change back to being correct,
but not all of them.

I wish I would have bought another program. This was a
flaw in Money 2003 and I assumed that it would have been
fixed in 2004 but I guess not.