|
|
From my experience the alldayevent properties is only used by OWA, what
happens with outlook is that it looks at the start and end time of the
appointment which for an all day event should be 12.00 AM adjusted to UTC
for the timezone your in (the best way to check is create a normal allday
event in outlook and have a look at what start and end times it uses). You
can test this yourself create an allday event in Outlook and then change the
time zone you'll see Outlook no longer detects this as an all day event.
You can submit feedback on any of the articles in MSDN by using the little
feedback form down the bottom of the page. (I think it would be a great idea
for them to document this the more people who ask the better.)
Cheers
Glen
"dominick" <dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20F43859-6511-4E4C-A65F-4DE8E8166E48@xxxxxxxxxxxxxxxx
>i dont set the start or end date for the alldayevent and the client and
> server are set to the same time zones... i dont explicitly set the
> timezone
> of the appointment when i run my script. the confusing thing is why on
> earth
> would OWA interpret the same exact appointment differently then Outlook.
> This sounds more like a bug then anything else, or maybe not a bug but the
> two applications interpret the SAME data differently. is there a
> microsoft
> article that discusses the impact of timezones on alldayevents or how mapi
> properties affect one another? also, if this is by design, can i get an
> explaination of why the timezone/alldayevent dependency exists?
>
> also in the mean time i have found a work around... if i set the start
> time
> to midnight of the date to midnight of the day after. BINGO it will show
> up
> as an alldayevent on the client side, but the exchange OWA side will look
> like a 24 hr appointment. no user is going to see the exchange OWA side
> so
> im not really worried about it.
>
> what really bothers me is that alldayevent=true does not mean the
> appointment is an alldayevent and this information is not documented
> anywhere
> in the msdn article that discusses the alldayevent property. can this be
> added in, im sure it would benefit a lot of people?
>
> thanks
> dominick
>
>
> "Glen Scales [MVP]" wrote:
>
>> Allday events are very time specific when your creating the appointment
>> with
>> your script are you setting the timezone field for the timezone you are
>> in.
>> If it looks okay on the server and not on the client are there
>> differences
>> in the timezone that is being use on the server to client. I would
>> suggest
>> you look more at what Mapi properties are being changed and set when you
>> create an appointment via Outlook and OWA vs your script. If you use
>> something like OutlookSpy you can do a watch of the properties that can
>> change when you modify the alldayevent check box which might point you in
>> the right direction.
>>
>> Cheers
>> Glen
>>
>> "dominick" <dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:9AC44E2C-3D6C-4910-9A85-549CEDC0CFD3@xxxxxxxxxxxxxxxx
>> >
>> > hi everyone,
>> >
>> > i am having a problem in exchange that i cant seem to figure out. i am
>> > adding a new calendar item via vb scripts. the calendar item gets
>> > added
>> > just
>> > fine and views just fine from owa on the exchange box. however if that
>> > calendar item was an all day event it does not show up as an all day
>> > event
>> > when viewed from outlook or owa on the clients machine, but views fine
>> > when
>> > on the exchange box. the only way i have managed to get outlook to see
>> > the
>> > all day event is to open up the appointment through owa (client or
>> > exchange
>> > side) or outlook (client side) and re save the appointment as an allday
>> > event. i ran a sql dump of the ADO.RecordSet object for the
>> > appointment
>> > and
>> > they are completely identical before and after the save, so i dont
>> > think
>> > that
>> > the data being stored in exchange is the problem. i think the problem
>> > may
>> > be
>> > that there is something installed on the exchange box that is not
>> > installed
>> > with outlook or simply that outlook has a bug that will somehow not
>> > pick
>> > up
>> > the all day event.
>> >
>> >
>> > does anyone have any ideas about this one?
>> >
>> > thanks
>> > dominick
>>
>>
>>
|
|