Yep, me too.  In fact I've had to create a special payee for these
called "Check or Checkcard" because no matter what I do, MoneyWell
will inevitably memorize a renamed payee based on the 'check' or
'checkard' prefix and then I see the same behavior the OP described
(renaming lots of different transactions to the same incorrect
payee...last one memorized).

It would be nice if there were a way to simply revert the outcome of
rename operation and restore the original payee from the downloaded
transaction info.

On Mar 27, 4:35 am, kmacstuf <[email protected]> wrote:
> Check your memorized transactions.  I've had this happen too (at least
> I think it's the same as what you're describing) and the culprit has
> always been a memorized transaction that just has the word "check" in
> it.  I go in to memorized transactions and delete the one that has the
> "check" alias.  Then things match up nicely and I don't get the wrong
> payee on my transaction.
>
> Kevin M
>
> On Mar 26, 11:50 pm, Lance <[email protected]> wrote:
>
> > ml,
>
> > Would it be possible for you to make a copy of your MoneyWell file and
> > then delete your Direct Connect info and all but the transactions you
> > mention above and modify any remaining sensitive info so it has
> > generic payee names and amounts?
>
> > Not that I don't trust Kevin, but I share your concerns about sharing
> > MoneyWell files. Given that the MoneyWell data file is unencrypted and
> > can contain quite a bit of sensitive personal info (including
> > usernames and passwords to access all your banking info!) I do not
> > think it would be a good idea for anyone to send these via unsecure
> > email.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "No 
Thirst Software User Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/no-thirst-software?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to