Well, a 0000-to-0000 appointment in Mountain Time would be 0200-0200 Eastern Time. You can check this, but I think the newest versions of Outlook handle this better.
Ed Crowley MCSE+Internet MVP Freelance E-Mail Philosopher Protecting the world from PSTs and Bricked Backups!T -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kent Sent: Friday, August 15, 2003 12:49 PM To: Exchange Discussions Subject: Calendar Problems We are using Exchange 5.5 on nt4.0 on 6 different domains(really sad) We have a calendar created on public folder store on a server in the eastern time zone on one domain. The users use it to show when different technology users will be off for the day or sick. We have a user adding an appointment from a server/client in central time zone on another domain. When The appointment is created in this calendar and it is made a all day event the originator's view shows as a single day. When anyone from the eastern time zone server views it it is shown as a 2 day event(forward a day). The reverse happens to the view if the originator is from the eastern server/client except the user in the central time zones views it as a 2day event(backwards a day) Let me know if you have any ideas why and or if there is a correction for this. Thanks Kent _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang =english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
