Birthdays all messed up

[Malfuric]

I just used Microsoft Office Online to publish my calendar. However, after it
published, I noticed that all of the birthdays in my calendar were now
starting at 6:00 a.m. and spanning two days. I'm in the Central US time zone,
which is GMT-6 so I'm assuming that has something to do with it. My questions
are: 1) how do I correct all of my birthdays without having to manually
correct them, and 2) why did this occur in the first place?

 

[Vince Averello]

Did you set the proper time zones everywhere (online & on your PC)? That
might have something to do with the problem

 

[Tiffany T. Barnes]

I have noticed the same problem. I thought it had to due with my Blackberry
syncing with my Outlook.
I am also Central Time and my computer and Blackberry both reflect that.

Any solutions?

Tiffany

 

[Vince Averello]

Does Outlook think it's in Central Time? Outlook has its own timezone
setting in the Calendar options: Tools menu > Options > Calendar

 

[Tiffany T. Barnes]

Yes, Outlook knows it is Central Time. I manage an executive heavy calendar
and do use two different time zones to assistant with meeting planning in
Outlook, but my priority time zone is Central.

 

[Vince Averello]

Hmmm, I wonder if the birthdays/holidays were imported when there was a
different time zone in play (probably by accident). You can try this manual
operation to fix things:
- set Outlook's timezone to whatever it takes to make the events normal
again (begin at 12:00A and end at 11:59:59PM)
- export the Calendar folder to a CSV file using the File menu > Import &
Export command
- delete the items from the calendar
- set the time to the correct one
- import the items

 

[jaydge]

2) because Microsoft wasn't smart enough to realize that a birthday field in
a contact should never have a start and end time... it should just be a date,
and that date should translate into an all-day calendar event on the correct
(original) date in any time zone - and more importantly, the date should
NEVER change in the contact itself. Outlook failed big time on this one.
Hopefully a future release will address this problem, but the feeling I get
is that MS cares more about flashy features than good basic functionality.