I don't know if my last message was posted or not, but I basically replied
saying I had tried the repair process and it didn't work. Well, right after
sending that message, I did a Quick Repair, and apparently that time, it
took. So, for the time being, my problem seems to have been solved.
Strange, though, because now that I think about it, I never tried a Quick
Repair, thinking this problem was too big of one to use anything less than a
full repair. The full repair didn't work and removing bills data didn't seem
to work (although for all I know, that might have been necessary before a
Quick Repair in order to solve the problem).

In any case, the Quick Repair seems to have worked. I mean I can actually
match things with transactions that are already in my register, which is
already bounds better than before. Thank you again for the response.

"johndog" wrote:

- quote -

You know, I've repaired my file numerous times, even Removed Bills Data
(which did nothing except make me enter all my bills and deposits in again).
The problem persists. I don't understand why this is happening. I also sent
an email in to Microsoft, but they have not replied yet, not even a form mail
"we've received your mail and will get back to you". It's really quite
annoying.

I'll try the round of file repairs again, but considering it hasn't worked
yet, I don't see it working this time. Thanks for the response though.

"johndog" wrote:

- quote -

On 2007-02-01, johndog <johndd[at]no-spam-bigfoot.com> wrote:
- quote -

How has that worked out? I would think that you run the risk of
continually getting that deleted transaction again everytime you get
new downloaded transactions. The reason I think this is that when
you delete the transaction, you also delete Money's record of the
OFX transaction ID. So to Money, it looks like a new transaction
that's not in your register. Of course, I don't know how Money works
under the covers. Does Money repeatedly download the transaction
that you deleted?

For reasons you describe, if I'm going to delete a duplicate transaction, I
always update the manual transaction (if necessary) and delete the
downloaded one.

- John

"Mark Horn" <mark[at]hornclan.com> wrote in message
news:slrnes41r6.v29.mark[at]home.hornclan.com...
- quote -

Keli'i,

I used to have the huge problem you describe where I couldn't even use the
'match' functionality even manually, and in fact it has come back several
time. But when this happens, I will 'repair' the file, and then the problem
goes away.

I suggest that you try the repair process and see if you can't still
manually match the transactions. (process below)

My complaint is that--even after repairing--the auto-match facility is
broken, and I wind up with two nearly identical transactions, both marked
'E' and 'Downloaded'. I know very well that one of them was already in the
register or was a scheduled payment. In this state I can still perform the
tedious manual match.


Here is the repair process:

- First, try File-> Repair-> Quick File Repair, and see if it fixes the issue.

- Second, try the "Corruption" section at http://umpmfaq.info/faq.html. I
followed those steps myself and it cured my enormous performance issues
immediately. Excerpt:

---------- Begin Quote -------------
Q) Can you tell me more about the remarkable new Nuke-the-Bills miracle
repair method?

[Relevant to Money2007 (v.16)]

A) Money 2007 introduced a new File|Repair option, File|Repair Money
File|Remove all Bills data. (Insiders have been referring to this as the
Bills Be Gone method. That seems too polite for the impact it has;
Nuke-the-Bills is our favorite term here at the umpmfaq.) This addition was,
apparently, an admission that Money can't keep the scheduled bills data sane
all by itself. This option has enabled dramatic improvements in performance
and significant reductions in files size for some users. At least one user,
the author, had serious "stability issues" (i.e., it crashed a lot) under
M06 that have not been seen in M07; this may be related to fixes in M07 or
it may be related to "corruption" in the file cleaned up by Nuke-the-Bills.
------------ End Quote -------------

I thought there was a KB on the subject, but I can't find it. Perhaps it
was this (Step 3)
http://support.microsoft.com/kb/182608/PT-BR/.


- John

"Keli'i Martin" <Keli'i Martin[at]discussions.microsoft.com> wrote in message
news:6CE3D4DD-7567-4533-999D-499C001ABE27[at]microsoft.com...
- quote -

Wow! I didn't experience this problem when I was testing M07.
That's a pretty annoying problem. I would think that you could just
delete the manually entered transaction. There are two pitfalls
that I can see to doing this:

1) If your transaction has a lot of splits (e.g. a paycheck)
then you'd have to manually enter all of those splits into the
downloaded transaction. What a PITA!

2) The "last paid" date in Bills & deposits would be wrong.

On the other hand, as long as you got the categorization correct,
your budget would be correct. You'd have budgeted $X for category Y
and you've have an entry of $X for category Y in your register.

On 2007-01-30, Keli'i Martin <Keli'i> wrote:
- quote -

This is sorta what is happening to me. I will enter a transaction manually
into my register. When my transactions are downloaded, Money creates a brand
new entry for the downloaded transactions, regardless of whether or not there
is a manual entry that matches the downloaded entry. This is already
different than the functionality from Money 2004, which is what I came from.

This wouldn't be a HUGE problem if not compounded with Money's current
inability to let me match this downloaded transaction with a manually entered
transaction. In Money 2004, I could click Change and be presented with a
list of entries that are already in my register that I could then match up
with the downloaded entry. In Money 2007, the list I am presented is not of
entries that are already in my register. I am presented a list of my future
bills and deposits and nothing else. I obviously don't want to match the
downloaded entry with a future entry. So what I am left with is a duplicate
entry in my register.

I've posted about this problem before, I have sent in an email to Support
(have not heard back yet), but I will continue to post in this newsgroup,
because it appears that this is not an isolated problem but one that more
people are seeing. I would go back to Money 2004 if I could, but the reason
I got 2007 is because downloading transactions stopped working, pretty much
forcing me to get this product if I wanted to continue using that service....

"johndog" wrote:

- quote -

I recently did the cure-all of 'Remove all bills data' and I've regularly
repaired my file. But I'm still seeing an issue of data not matching, and
manually entered transactions mysteriously showing up with 'E' or
'Downloaded' status.

Here's what I think is going on:

1) I enter a bill into my register. It shows up un-reconciled.
2) I download a statement from the bank, and this includes a transaction
that matches the bill entered in step 1 perfectly (date, amount anyway)
3) I go into the register, and Money has *not* matched the downloaded to the
existing transaction. Instead, they are both marked with an 'E', with the
downloaded one showing up bold and the prior one not.

What??? How can my existing transaction be marked 'E' and 'Downloaded' when
it was entered from scheduled bills???