Will wrote:

- quote -

It sounds like you're suffering from the common "sumpn's corrupted in
the database" problem. One solution is to delete the thing you think is
corrupted, and re-enter it. This is a standard solution in databases of
all types.

In this case, you could create duplicate transactions for those with
"999999GY9", except with a different name, then delete the ones with
"999999GY9". A more extensive solution would be to delete the entire
account that has those transactions, then re-enter them.

There's also the possibility that there aren't really any transactions
with "999999GY9"; there's just some phantom data that you can't get to.
Perhaps you could repair the money file:
File> RepairMoneyFile> QuickFileRepair or
File> RepairMoneyFile> StandardFileRepair.

--
Steve Bell
New Life Home Improvement
Arlington, TX

I have Money Home & Business 2007 and I'm trying to use it to help parents
balance their IRA account. The software downloaded all transactions and
when I go to Read Statement I am going into an endless loop.

The first investment that comes up is a bond. Money tells me that "This
investment is already in my investment portfolio with a different name...."
If I select the radio button option that corresponds to using the existing
investment and hit Next, nothing happens. I then select Next again with
the same radio button selected and I get a modal dialog:

"Do you want to change the CUSIP for <investment name> from NONUMBER to
999999GY9 to match the statement?

Click Yes if you assigned the wrong CUSIP and want Money to fix it....."

It doesn't matter whether I click Yes or No, either option gets me back into
the same two step loop described above, and the investment is never
processed off of the statement.

If I instead opt at the beginning to select the different radio button
corresponding to "Add this as a new investment...." I get another error
message "Money can't create this new investment because another investment
with the same name already exists."

Any ideas on possible causes for this? Sure looks like a bug.

--
Will