"Bert Wicks" <> wrote in message
news:...
> Hello Noel,
> Thanks very much for your advice.
> You are quite right - I should not have started multiple threads, and
> will start no more on this subject.
> I will endeavour to check out your suggestions today.
> It is heartening to me that you do not experience the problem on XP SP3.
> My evidence was that the same problem arose on two different computers
> both running XP SP3 - so I assumed that there must be some
> incompatibility between WLM and XP.
> I will now follow your advice and look more closely locally. I will
> report back but it may take me a couple of days to do so.
OK. You will probably have noticed in one of your other threads that David
Gould [MSFT] points out that the fix I mentioned won't go live until the
next release (i.e. Wave 4, version probably 15 of WLMail), so the 'first
day of the week' bug is still active and may be biting you. The problem
with working round it is the way the calendar synchronizes - changes to the
server copy eventually propagate to the local one, and vice versa. I can
only suggest the following, with no guarantee that it will work:
(a) Close down WLMail.
(b) Go to
http://calendar.live.com and access the problem calendar.
(c) Delete all instances of the dodgy event - check a few months ahead that
they're all gone.
(d) Change the First Day of the Week option to Monday and save the change.
(e) Change it back to Sunday and save the change.
(f) Sign out of calendar.live.com and close down your browser.
(g) Start WLMail and wait for its initial processes to complete - watch the
right-hand end of the status bar.
(h) Select Calendar mode and see if the problematic event has gone away. If
it hasn't, wait an hour or two, then close down and restart WLMail again
(this will force another sync with the online calendar).
(i) Repeat (h) until the event is gone.
(j) Cross your fingers and re-insert the event on the right day.
--
Noel