Good to hear that you figured it out.

--
Michael Gordon
MVP


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:O1YxYt$wGHA.4872[at]TK2MSFTNGP02.phx.gbl...
- quote -

If you have online banking and an apay/epay payee is downloaded from the
bank before being created in Money, I think it's possible for them to be an
exact duplicate of an existing non-apay/epay payee. That's because they're
really not duplicates, on some hidden unique identifier. (I'm guessing here
but have observed duplicate payees.)
--
Chris Cowles
Gainesville, FL



"Anna" <rhodesbiz[at]bellsouth.net> wrote in message
news:1156084618.258641.148260[at]i3g2000cwc.googlegroups.com...
- quote -

Anna wrote:
- quote -

If you add a payee one time which is exactly the same as an
existing one, Money will ask you if you want to merge the two payees.
If you say "NO", Money will create a second payee with the same name.
Not sure how Money decides which one to use in future transactions but
it might be last one you assigned. If you manually write in the payee
name instead of picking it off the list, that might have an impact too.
Anyway, you solved your problem. Key thing is not to assign the same
payee name more than once in Money. Steve

I opened a backup to double check, but the payees were EXACTLY alike in
name, spacing, spelling. The only difference I could find was that one
payee had account and phone# listed and the other did not. But the
Payee NAMES were identical. No extra spaces or anything that I could
see. I checked the details for each and both of the payees had multiple
transactions associated with it. One payee I had used from 1999-2002,
with a few transactions this year. The other payee had transactions in
it from 2002-2006. These duplicate payees have been there a long time
(I guess I need to clean out my payee list. But merging these two
payees fixed the problem. Funny it never created a problem before from
99-06, just now when the Loan Payment problem emerged in M07. I am
guessing that Duplicate Payees and the new Loan Payment problem
conflict in some strange way.

Anna


Dick Watson wrote:
- quote -

That's an interesting observation. Thanks for posting it. When you say
"Duplicate Payee" do you mean two slightly different payee names listed in
Payees and the Loan Payment was using one of these?

"Anna" <rhodesbiz[at]bellsouth.net> wrote in message
news:1156047591.357644.120600[at]m79g2000cwm.googlegroups.com...
- quote -

Back to Strange Problem:

I finally figured out WHY my Loan Payment in M07 would not move down to
the next month in the Bill Summary after Entering it into the Register.
I had a Duplicate Payee for this Loan Payment in Payees. Once I moved
the Duplicate Payee to its twin, the Loan Payment slid right down from
August to September as it should. I've had duplicate payees many times,
but never has it created this strange response.

Anna




Dick Watson wrote:
- quote -

Aha! I get it finally.

I just groups.googled that message ID. We aren't even talking about the same
message. You are referring to one that I never thought was lost and didn't
resend. I was/am referring to a message, data provided earlier including
posting time, that disappeared into the ether at msnews.microsoft.com.

The one that disappeared into the ether was a variant on
eX9ks5swGHA.1288[at]TK2MSFTNGP02.phx.gbl. Note that when that message says "My
first attempt to reply apparently got swallowed..." I was referring to my
first attempt to reply to
1155871144.196850.265260[at]m73g...oglegroups.com not to my successful
attempt replying to 686C0DE8-AA9D-4921-982C-D3F249519C5B[at]microsoft.com in
the form of #GRnxJnwGHA.4944[at]TK2MSFTNGP02.phx.gbl.

"Michael Gordon, MVP" <gordonm[at]denison.edu> wrote in message
news:%2367wcg%23wGHA.1288[at]TK2MSFTNGP02.phx.gbl...
- quote -

Don't know what to tell you. It didn't get back to any of my three OE
msnews.microsoft.com clients (desktop, laptop, work machine) nor do I see it
in groups.google.com nor the MS Support web interface. That's why I
re-posted.

I've also played around with missing messages before enough to know that
there are choices of words/phrases that *do* get swallowed at
msnews.microsoft.com. That's not paranoia, it's experience. When I posted
the full text FAQ, sometimes new questions/answers would cause the whole
posting to get swallowed. I'd do binary searches with parts of the message
in the microsoft.public.test group until I'd get down to, say, a part that
was 50 or 100 lines long. Then looking for phrases/words like "e a s y m o
n e y" (stretched here precisely to avoid getting swallowed) would lead me
to re-word/re-phrase until the small part posted and could be
seen/retrieved. Note that the wording of my last paragraph in the pair of
messages we are discussing is different. I didn't change them for the fun of
it and only one of the two--the second one--is in groups.google.com and is
visible on the MS Support web interface. I have also seen in the years since
I posted the full text FAQ.

I have also seen the case where messages get on one of the msnews servers
but not all of the others. Randomly people will/won't see it depending on
which server they got redirected to when they connected. I have also seen
the case where you can get a message *very* soon after it is posted but not
subsequently. My understanding--I'm not an NNTP expert by any means--is that
the newsreader does not re-query for message numbers below the highest
sequence number it has seen from the server previously, you can see a
message if you downloaded it in this interim period even though it isn't on
the server if you reset the sequence and downloaded the new headers. You can
also see this sometimes (rarely) if you d/l headers, go off and putz around
for a while, then come back to see some spam-like subject and try to
download the message and get expired/removed from server errors. I guess my
point is that seeing it in your newsreader "right now" may only mean that
it's cached locally even though it's not on the msnews servers anymore.

"Michael Gordon, MVP" <gordonm[at]denison.edu> wrote in message
news:%2367wcg%23wGHA.1288[at]TK2MSFTNGP02.phx.gbl...
- quote -

Hi Dick -
I don't see it via the web interface (which I never use), but I am seeing it
right now via the newsreader as
Message-ID: <#GRnxJnwGHA.4944[at]TK2MSFTNGP02.phx.gblNewsgroups: microsoft.public.money
NNTP-Posting-Host: h-69-3-79-16.dnvtco56.dynamic.covad.net 69.3.79.16
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
Xref: TK2MSFTNGP01.phx.gbl microsoft.public.money:206979


--
Michael Gordon
MVP


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:%2343JjtzwGHA.4972[at]TK2MSFTNGP05.phx.gbl...
- quote -

Not on the server I'm getting messages from at home, nor the one I got
messages from at work, nor in groups.google.com, nor when I looked just now
in the web interface at
http://www.microsoft.com/communities...t.public.money.

This is the one I was referring to. Do you see it? Did you download shortly
thereafter? (Sometimes messages get there and then get gone.)

From: "Dick Watson" <littlegreengecko[at]mind-enufalready-spring.comNewsgroups: microsoft.public.money
References: <F253554D-510E-4B91-982E-8F26CCB9252F[at]microsoft.com<OCHunkbwGHA.4140[at]TK2MSFTNGP03.phx.gbl<eRClIRiwGHA.1284[at]TK2MSFTNGP05.phx.gbl<686C0DE8-AA9D-4921-982C-D3F249519C5B[at]microsoft.com<1155871144.196850.265260[at]m73g2000cwd.googlegroups.comSubject: Re: 2 Strange Problems
Date: Fri, 18 Aug 2006 06:24:33 -0600
Lines: 34
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Original

I may be paranoid, but I'm not crazy. Yet.

"Michael Gordon, MVP" <gordonm[at]denison.edu> wrote in message
news:%23kOmuUywGHA.5064[at]TK2MSFTNGP06.phx.gbl...
- quote -

Control your paranoia, Dick - it's out there and easily visible.

--
Michael Gordon
MVP


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:eX9ks5swGHA.1288[at]TK2MSFTNGP02.phx.gbl...
- quote -

My first attempt to reply apparently got swallowed by Microsoft's spam
filters.

"Anna" <rhodesbiz[at]bellsouth.net> wrote in message
news:1155871144.196850.265260[at]m73g2000cwd.googlegroups.com...
- quote -

I recreated every one of my bills in M07 and do not see this behavior. I
wonder what else is going on for you. Is this an Apay?

- quote -

Because they want to because lots of businesses are willing to spend lots of
$ and demand sophisticated software and they can make money developing it
that way.

- quote -


Because they don't want to because not all that many home users are willing
to spend only tiny amounts of $ on un-sophisticated software and even then
lots of them complain in lots of ways--like opening expensive support
cases--that even as it is, the product is still too sophisticated. At that,
Microsoft probably still hasn't made a dime on this product and they've been
trying almost fifteen years.

There is one OTHER issue I am having with this Loan Payment problem
that isn't mentioned in the Microsft KB article. I have 3 Loan Payments
scheduled each month(Car, Home, Home Equity). The Home Equity (EQ)
account was created after upgrading to M07. This newly created Loan
Payment has an additional problem that I do not have with the old Loan
Payments. From the Bills Schedule, when I click on Enter in Register, I
get the same problematic Add Transaction box as I do when I go to enter
the other two loan payments. So, I change the date, choose the checking
account, and click OK. The transaction is entered correctly into my
checking account and the EQ account.

HOWEVER, when I return to the Bills Schedule, the Loan Payment for the
EQ account is STILL there for the current payment. In other words, when
I clicked OK on the Aug. 15 payment, it is entered as Aug. 15, BUT it
is still listed to be paid on Aug. 15. This bill does not move to the
next month. And for every time I click, a new entry is created in the
register for Aug 15. But in the Bill Scheduler, it never moves on down
to the next month.

I have deleted and recreated this bill several times, all with the same
results. The Loan Payments that were created before the upgrade at
least will move down to the next month after entered.The newly created
one acts differently for some reason.

My solution is to just enter it from the Calendar and then it moves to
the next month.

I was glad to see MS finally admit that scheduled "Loan Payments" were
a problem in the KB article. Maybe when (if) they fix the problem, it
will solve this additional problem i am having as well..... or maybe
not.

I just do not understand how MS can make sophisticated software like
Excel that works so well (for me anyway), but CANNOT seem to get MS
Money software right!

Anna


Dave wrote:
- quote -

Can't say for sure, but if history is a guide, the scheduled loan payments
entry behavior may be here for versions to come--certainly history would
suggest a mid-stream fix for this was highly unlikely. One of the prime
reasons they won't ship a patch is that you *can*, with careful data entry
and a pain every time, get completely around this problem.

As to the second problem, I don't think it's a Money problem--or at least
not one a defect in the reporting code can fix. I'm betting it's some
problem with your data file. (Do the sample file reports run on your
machine?) Why the repair options don't solve it and how to solve it is
another question I don't have great answers to. All reports? (Really?) If
just some, there may be techniques you can use to maybe isolate the issue to
specific data. (The ones I'm thinking of worked in M04--where you could
customize a report without actually opening it--but I'm not sure you can do
this in M05+ and just closed all the Money apps down so can't readily test
just now.)

"Dave" <Dave[at]discussions.microsoft.com> wrote in message
news:686C0DE8-AA9D-4921-982C-D3F249519C5B[at]microsoft.com...
- quote -

Is there going to be a patch to fix this? What about the other problem? I'm
starting to think I should move to quicken. I've been a loyal money user
since the late 90s, but these kind of issues are really frustrating. These
are incredibly important pieces of why I use the software.

"Mark" wrote:

- quote -

<rantWow. The MSKB says it's a "problem" "because of changes that were made to
the Money 2007 program." This poster must have misunderstood what Microsoft
Support told her:
http://groups.google.com/group/micro...c2af5f0?hl=en&

Speaking as someone who wasn't involved in the beta test, I've got to assume
that such a rapid appearance of an MSKB item, with an uncharacteristically
frank admission that it's broke and Microsoft broke it, indicates this
problem was known long before Microsoft shipped the retail code.

That brings up the question of whether it was known to Microsoft before or
during the beta test and, more to the point, why it shipped this way. How
bad does a bug have to be to get fixed if it's still there when the code
goes to beta test? > 50% of users can't get past install? Why even do the
beta tests?

Of course, it also brings up the question of what kind of test suite is used
before the code gets to beta test. This isn't an obscure behavior or
intermittent case. I'll likely see it 52 times this year. (I don't want to
even think about how many times I might have to see it in M08 and M09.) I'd
might go to the "automatically enter" workaround except I classify my loan
payment transactions and, fully 13 years after I first posted the
suggestion, classification is still not supported for scheduled loan
payments.

Also note the MSKB says "Today's date and the account field may not be
automatically filled in." Today's date IS automatically filled in,
regardless of the date in the scheduled item. Oh, and if you let it get in
the register this way, the interest calc in the transaction gets mucked as
well.

Just venting.
</rant
"Mark" <abcd[at]abcd.com> wrote in message
news:eRClIRiwGHA.1284[at]TK2MSFTNGP05.phx.gbl...
- quote -

There's a new KB article about this:
http://support.microsoft.com/kb/923030/en-us


"Dick Watson" <littlegreengecko[at]mind-enufalready-spring.com> wrote in
message news:OCHunkbwGHA.4140[at]TK2MSFTNGP03.phx.gbl...
- quote -

This is a new "feature". Support told someone that we wanted it this way and
it's better this way. Seems like it's broke to me, but there you have it.

"Dave" <Dave[at]discussions.microsoft.com> wrote in message
news:F253554D-510E-4B91-982E-8F26CCB9252F[at]microsoft.com...
- quote -

OK, These problems only started when I moved from 2005 to 2007 (why did I
ever do that...)

First off, I can no longer look at reports. It will usually display one,
but then get hung up on the others and just says loading... and it never
loads. I've tried repairing the file and it works maybe once or twice, but
then back to the same old stuff - same thing when I reinstall - I get one
time to look at reports.

Second, I have my mortgage. I changed the checking account I want to pay
from - seems simple right, now every time I click the "enter transaction" or
whatever it is called on the bills screen it has the wrong date for the
payment - it always uses todays date, not the next loan payment date, and it
has no account in the list to pay from - even though all this information is
in there properly if I go to edit bill series.

I thought software was supposed to get better as you created newer versions.
This looks exactly the same as 2005, but with many more bugs.