If you have both buys and sells for the same investment, and want to adjust
old transactions, the easiest way to avoid this error may be to enter a
"bogus" Buy dated well before all of the transactions for a huge quantity.

This overcomes the issue where you have a Sell in the register but haven't
yet entered the initial Buy (or that purchase was dated after the sell)

Then after you're all done (and confirm that the ending postition - current
number of shares is only off by the "bogus" purchase amount), then you can
delete that bogus Buy.

Another thing, since there could be some rounding difference, if you are not
entering whole shares, then be sure to enter the share quantity exactly and
let money calculate the price per share. i.e. if you purchased $100 worth of
shares priced at $33.33 enter it as 3.333 shares, put in $100 for the total
and let Money calculate the price as $33.33333...

-Mark

"Marianne Seckel" <marianne.seckel[at]us.army.mil> wrote in message
news:%23QSYBxn7EHA.1400[at]TK2MSFTNGP11.phx.gbl...
- quote -

In microsoft.public.money, Marianne Seckel wrote:

- quote -

I was only speculating. Yours is not a common problem.

If the hypothesis of RemoveShares transactions turns out to be
right, you might View:sortByActivity the register. That would put
them together. I would then void each (or at least the most recent)
and make your changes. After things are right, you can delete the
voided transactions. The advantage of keeping them voided for a
while is that you can un-void, turn them into Sell transactions as
appropriate, or whatever seems appropriate.

When making big changes it never hurts to have an extra backup file.

Cal,

thanks for the quick response. That makes sense I'll change my recurring
transactions. However, is there any way to get past this error message and
clean up my last few months?

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

In microsoft.public.money, Marianne Seckel wrote:

- quote -

The way I would handle this is to enter/change the debiting to a
Transfer:MutualFundAccount(cash) via using the SPECIAL categories at
the bottom of the Category list.

Then on the 5th I would enter the Buys with the investment cash
account being the source of the funds.

- quote -

That is strange. The only thing that comes to mind is that the
mutual fund account is somehow downloading balance information.
Money offered to do RemoveShares to make your holdings match what
was downloaded as fund holdings, and you accepted.

It could be something else happening, but I can't think of what it
would be. Your method of entering estimated Buy transactions and
then changing the Quantity field later seems like it should work
without error.

WinXp/MM2003

I need some expert advice. I have been playing catchup since I now have
some time to dedicate to my MS Money this week and I keep running into this
very frustrating problem.

My checking account is debited for investment purchases every month. A few
days after that, my funds purchase new shares in each of several funds from
that same transaction. The way I have it set up, I have one transaction
which is split to make these purchases.

for example
on 1 December, my checking account is debited $100. Say, on december 5th,
my fund company actually buys the shares for 4 funds at the closing price
for that day (fund1 - $25, fund2 - $25, fund3 = 35, fund4 = $15).

As a result of this, I have to go back to update the actual "buy" figures
of investment fund purchases for price and quantity.
When I make the changes, I get an error message that says "the changes you
are making will cause the share balance of XXX to become negative at some
point Please adjust your transactions to avoid this." It is not the same
fund every time, and does not necessarily reflect the fund I am updating. I
have tried to fnd info on this, but have only found suggestions relating to
"sells". Why am I getting this error when I am buying and doing nothing to
remove shares? Any help on this would be great!

thanks,

M. Seckel