2005 Problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jason - 13 Oct 2004 20:27 GMT

When you publish a calendar to a web page Jan 1, 2005 starts on Friday
instead of Saturday. Does not matter what time frame you use all of 2005 is
moved foward by one day.

Could one of you Microsoft guys look at this and get a fix in the works. I
have tried this from 3 different PC's with the same results.

Reply to this Message

Milly Staples [MVP - Outlook] - 17 Oct 2004 18:32 GMT

This is not Microsoft. Try contacting them directly from a "contact us"
link on any Microsoft web page.

Signature

--?
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. Due to
the (insert latest virus name here) virus, all mail sent to my personal
account will be deleted without reading.

After furious head scratching, Jason asked:

| When you publish a calendar to a web page Jan 1, 2005 starts on Friday
| instead of Saturday. Does not matter what time frame you use all of
| 2005 is moved foward by one day.
|
| Could one of you Microsoft guys look at this and get a fix in the
| works. I have tried this from 3 different PC's with the same results.

Reply to this Message

akm - 24 Oct 2004 23:41 GMT

This is a well documented (on web boards) problem.
I posted the same question at many different web boards including on 9/17
at...

http://www.microsoft.com/exchange/community/NewsGroups/default.mspx?query=2005&d
g=microsoft.public.outlook&cat=exchange&lang=en&cr=US&pt=&catlist=C9163434-DE68-
4F9E-A3B5-4D2FB01B697F&dglist=&ptlist=&exp=&sloc=en-us

The problem is I havent seen a solution or any indication that there is
going to be a solution.
Dont know how to get MS to respond.
Any ideas besides trying their support page (there you have to pay them to
tell them that they have a bug to fix)?

> This is not Microsoft. Try contacting them directly from a "contact us"
> link on any Microsoft web page.
[quoted text clipped - 5 lines]
> | Could one of you Microsoft guys look at this and get a fix in the
> | works. I have tried this from 3 different PC's with the same results.

Reply to this Message