Re: Completed tasks not removed from PPC

I presume this is an issue described in this article:
http://support.microsoft.com/default...b;en-us;256077

It mentions ActiveSync 3.6, but I have 3.8 and am having the same issue.
Recurring tasks are very important in realisation of my variant of the GTD
system (after David Allen's book) and it really is annoying because attempts
to do something at random just generated lots of completed tasks with the
same content...

I hope that the workaround offered in the article will at least somehow
relieve this problem, until it finally gets fixed in new ActiveSync...
___________________
Maximilian

"Paul" <> wrote in message
news: oups.com...
> Hi,
>
>>From a quick web search, a number of posts seem to provide plenty of
> evidence of this problem. To recap, setting a task as completed in
> Outlook does not result in it being set as completed (and subsequently
> removed) from the PPC device. However, setting it as completed on the
> PPC does result in the Outlook task being set to completed.
>
>>From these same posts, the most typical "solution" to this problem is
> to change the default setting from "Synchronize only incomplete tasks"
> to "Synchronize all tasks". Frankly, this doesn't make much sense to
> me. It seems like the natural assumption on how to interpret the former
> option should be for it to read: "Synchronize all tasks, but remove
> completed tasks from the PPC device". Otherwise, what would be the
> point of this option? In which logical scenario would someone actually
> want items marked as completed on the desktop not to sync to the PPC?
> But if set completed on the device then sync it to the desktop? This
> smells of a bug to me.
>
> I've observed this problem in ActiveSync 3.8 and I'm pretty sure I saw
> it in 3.7. What's more is that I'm pretty sure I've seen ActiveSync
> behaving as I'd expect (following a fresh install perhaps), but then at
> some point something happens and it starts misbehaving in this way.
> However, I've not been able to determine what gets it started.
>
> If anyone from Microsoft is reading this, is this a known bug? Is there
> plans to fix this? It is oh so annoying.
>
> Cheers,
> Paul
>