Re: migrating outlook VBA application from office xp to office 2003

microsoft.public.office.developer.outlook.vba

20 Nov 2004 7:55 AM

Michael Bauer

Hi Sue,

> intrinsic Application object, so that you can avoid security prompts
as much
> as possible.

are there any exceptions?

--
Viele Grüße
Michael Bauer

"Sue Mosher [MVP-Outlook]" <sue***@outlookcode.com> wrote in message
news:uzQHJdnzEHA.3908@TK2MSFTNGP12.phx.gbl...
> The main thing is to make sure that all your Outlook objects derive
from the

Otherwise, VBA is the same in all versions, except for small
Show quote

> additions to the object model.
>
> --
> Sue Mosher, Outlook MVP
> Author of
>      Microsoft Outlook Programming - Jumpstart for
>      Administrators, Power Users, and Developers
>      http://www.outlookcode.com/jumpstart.aspx
>
>
> "Kamesh" <Kam***@discussions.microsoft.com> wrote in message
> news:E65504B0-BD60-44FF-BD13-6DD3D5CA321C@microsoft.com...
> > Hi, we are having a outlook VBA application, we need to migrate it
from
> > office xp to office 2003, how can I do it?, what are the changes I
need to
> > do?, I'm a .NET guy, I'm new to VBA programming, please help me in
this.
> >
> >
> > Thanks in advance
> >
> > Kamesh.
>
>

20 Nov 2004 2:47 PM

Sue Mosher [MVP-Outlook]

Well, any CDO code that accesses blocked properties or methods will trigger
security prompts, of course. The one exception I've found in Outlook code is
that, in at least some cases in OL2003 SP1, the MailItem object passed by a
rule isn't fully trusted. I'm still looking into that.

--
Sue Mosher, Outlook MVP
Author of
     Microsoft Outlook Programming - Jumpstart for
     Administrators, Power Users, and Developers
     http://www.outlookcode.com/jumpstart.aspx

Show quote

"Michael Bauer" <mi***@t-online.de> wrote in message
news:O3ruvjtzEHA.3376@TK2MSFTNGP12.phx.gbl...
> Hi Sue,
>
>> intrinsic Application object, so that you can avoid security prompts
> as much
>> as possible.
>
> are there any exceptions?
>
> --
> Viele Grüße
> Michael Bauer
>
>
> "Sue Mosher [MVP-Outlook]" <sue***@outlookcode.com> wrote in message
> news:uzQHJdnzEHA.3908@TK2MSFTNGP12.phx.gbl...
>> The main thing is to make sure that all your Outlook objects derive
> from the
> Otherwise, VBA is the same in all versions, except for small
>> additions to the object model.
>>
>> --
>> Sue Mosher, Outlook MVP
>> Author of
>>      Microsoft Outlook Programming - Jumpstart for
>>      Administrators, Power Users, and Developers
>>      http://www.outlookcode.com/jumpstart.aspx
>>
>>
>> "Kamesh" <Kam***@discussions.microsoft.com> wrote in message
>> news:E65504B0-BD60-44FF-BD13-6DD3D5CA321C@microsoft.com...
>> > Hi, we are having a outlook VBA application, we need to migrate it
> from
>> > office xp to office 2003, how can I do it?, what are the changes I
> need to
>> > do?, I'm a .NET guy, I'm new to VBA programming, please help me in
> this.
>> >
>> >
>> > Thanks in advance
>> >
>> > Kamesh.
>>
>>
>

20 Nov 2004 3:39 PM

Michael Bauer

Thank you, Sue. I´m looking forward reading more details at your site
one day.

--
Viele Grüße
Michael Bauer

Show quote

"Sue Mosher [MVP-Outlook]" <sue***@outlookcode.com> wrote in message
news:umvMRGxzEHA.2716@TK2MSFTNGP14.phx.gbl...
> Well, any CDO code that accesses blocked properties or methods will
trigger
> security prompts, of course. The one exception I've found in Outlook
code is
> that, in at least some cases in OL2003 SP1, the MailItem object passed
by a
> rule isn't fully trusted. I'm still looking into that.
>
> --
> Sue Mosher, Outlook MVP
> Author of
>      Microsoft Outlook Programming - Jumpstart for
>      Administrators, Power Users, and Developers
>      http://www.outlookcode.com/jumpstart.aspx
>
>
> "Michael Bauer" <mi***@t-online.de> wrote in message
> news:O3ruvjtzEHA.3376@TK2MSFTNGP12.phx.gbl...
> > Hi Sue,
> >
> >> intrinsic Application object, so that you can avoid security
prompts
> > as much
> >> as possible.
> >
> > are there any exceptions?
> >
> > --
> > Viele Grüße
> > Michael Bauer