You can actually run the two versions side by side, but 07 will take over
file associations. Therefore, if/when you remove 07, the easiest thing would
be to reinstall 06.
Let us know whether 07 works for you.

--
Michael Gordon
MVP


"lkaplan329" <lkaplan329[at]discussions.microsoft.com> wrote in message
news:916E9962-5218-4657-8D8E-0C732FE664F1[at]microsoft.com...
- quote -

I am not sure that fits my situation, as the DTSTART and DTEND sent by the
Money client are correct, but the server drops the transactions from the
DTSTART date, and sends the rest.

In any case, maybe I'll try the 07 demo and see if it goes away. Am I able
to load and trial the 07 demo without uninstalling or losing my 06
installation ? How does that work ?

In general, I am miffed that after spending $30 to buy the 06, I have to
spend another $30 to buy the 07 to fix a bug.

Thanks again Michael for all your help,

Larry

"Michael Gordon, MVP" wrote:

- quote -

Hi Larry - Sorry I wasn't clearer. I believe the problem begins with a FI
sending an invalid DTEND, which Money then picked up and went with.
Following up on what I said earlier: if Smith Bartney or any other FI sends
a DTEND for next year, Money won't stop asking for transations that are
earlier than that date and thus missing all the statement data until that
future date arrives. Money now asks for all transactions fromt he date of
the last download if that's less than the DTEND value.

This information comes in part from my experience and in part from the the
product group in Redmond. Yes, indeed, this is a hobby -- by profession, I'm
a historian......
--
Michael Gordon
MVP


"lkaplan329" <lkaplan329[at]discussions.microsoft.com> wrote in message
news:8C56B37A-8631-496B-8D5F-E24E8E6219AB[at]microsoft.com...
- quote -

Hi Michael,

Thanks again for the reply. I am a little confused by your explanation.

The DTEND is generated by the client end. In my case, on 8/25, the client
side sent a request with DTSTART=8/23 and DTEND=8/25. So, in that case, 8/25
is not in the future. Also, as the client generates the request, i.e.
Money06, what do you mean "it ignores...".

Sorry to be a pest; I like to understand things. Assuming your explanation
is correct, perhaps this behavior was only true in 06 - maybe uSoft was
thinking they fixed an error, while uncovering latent bugs in the FIs, they
changed it back.

I am a software engineer and I can see how this would happen.

Where did you get the confirmation of this - by trying it yourself, or is
there an article on this phenomenon somewhere.

That said, I am unhappy enough to buy 2007 - I'll see if I can find a coupon
for it somewhere. It just came out recently, didn't it ? The stores here
are still selling 2006.

Again, many thanks - I assume you do this as a hobby. In any case, I am
indebted to you for your kind help.

Larry Kaplan


"Michael Gordon, MVP" wrote:

- quote -

Hi Larry,
Given that you don't want to upgrade to 07, you may not want to read further
<g> . I can confirm that Money 2007 fixes the problem. It ignores a DTEND
that's in the future and only accepts a date that's not higher than the last
transaction or beyond today.
Personally I think this is one of several improvements in 2007; why don't
you download the trial and take a look at it?


--
Michael Gordon
MVP


"lkaplan329" <lkaplan329[at]discussions.microsoft.com> wrote in message
news:8C8864AE-A3B2-4B77-B1F0-C2791808DB73[at]microsoft.com...
- quote -

Hi Michael,

Many thanks for your kind reply. It is too bad one cannot modify the "last
updated" field - that would solve this and be very useful in other re-syncing
situations.

For what it's worth, I did try disabling and re-enabling online services,
and that didn't do the trick. I have emailed Smith Barney with a detailed
description of the problem, but frankly I don't expect to hear much from them.

I was very happy with Money 2003, but it "expired" after 3 years - a warning
said updates would no longer be supported. So, I very reluctantly bought
2006 - maybe that was a mistake. I am not prone to spend cash for another
update to 2007 right now.

Is there any other compelling reason that 2007 is better than 2006 and worth
the money to upgrade ?

Thanks again for your time and trouble to answer. It saves me more wasted
time...

Regards,

Larry Kaplan


"Michael Gordon, MVP" wrote:

- quote -

Hi Larry,
This is a situation that came up with some frequency in Money 2006. As you
suspect, the problem lies on the provider side (e.g., Smith Barney in your
case). Sometimes contacting the FI works, sometimes disabling online
services and then reenabling it works. For what it's worth, I've not seen
the problem with Money 2007 which -- I know -- doesn't make sense if the
problem is on the server side.

--
Michael Gordon
MVP


"lkaplan329" <lkaplan329[at]discussions.microsoft.com> wrote in message
news:BE0412B0-66B2-45C3-BEF0-993AB0A8AC54[at]microsoft.com...
- quote -

I have been using Money 2003 Deluxe for 3 years without problem. Recently I
updated to Money 2006 Deluxe.

One of my brokerage accounts is now losing transactions. I captured the log
files, and I can see that Money seems to be asking for the right dates, for
example:

<DTSTART> 20060824
<DTEND> 20060825

The last update was 8/23, so this would appear correct.

In the RS file, these dates are also recorded. But the transactions start
on 8/25, not 8/24. And the 8/24 transactions are not tranmitted.

Oddly, this worked fine in Money 2003.

Is there a way to reset or change Money's "last updated" field, so I can get
all the transactions ?

Any help or advise would be appreciated.

It seems the problem might be with the brokerage firm (Smith Barney), but I
hesitate trying to get them involved.

Many thanks,

Larry Kaplan