Re: disable security warning by accessing different object model

Re: disable security warning by accessing different object model

Hi Sue,

I have a macro which is in excel to read other users inbox. I am getting the 
security warning while trying to read the inbox.

Please let me know if there is a way to avoid this warning, when the code is 
not written in outlook

Thanks


"James B" wrote:

> omg how easy was that, changed it to this and voila
> Set myOlApp = Application
> 
> BTW I found that line in another post of yours lol
> http://help.lockergnome.com/office/avoid-security-popup-Outlook-2003-ftopict707774.html
> 
> "Sue Mosher [MVP-Outlook]" wrote:
> 
> > 
> > Never use a statement like this in Outlook VBA: 
> > 
> >     Set myOlApp = CreateObject("Outlook.Application")
> > 
> > Instead, derive all your Outlook objects from VBA's instrinics Application object.
> > 
> > -- 
> > Sue Mosher, Outlook MVP
> >    Author of Configuring Microsoft Outlook 2003
> >      http://www.turtleflock.com/olconfig/index.htm
> >    and Microsoft Outlook Programming - Jumpstart for 
> >      Administrators, Power Users, and Developers
> >      http://www.outlookcode.com/jumpstart.aspx
> >    
> > "James B"  wrote in message news:965721BF-CCAD-4975-88B8-F66F11249F19@microsoft.com...
> > > Hello, sorry for the lack of info.  I am using Outlook 2003 on XP with all of 
> > > the latest patches.  My code is VB and saved in a .OTM file (I access it by 
> > > clicking Tools > Macro > Visual Basic Editor from the Outlook menu).  I have 
> > > self signed the code and my current security setting is set to High.  
> > > 
> > > I created a function that scans my inbox and puts emails into certain 
> > > folders, bascially just moving emails around.  I then created a shortcut 
> > > button on my toolbar to activate this function.  What I would ultimately like 
> > > to do is disable the security warning that comes up when I click on this 
> > > button, it is the standard warning "A program is trying to access e-mail 
> > > addresses you have stored in Outlook.  Do you want to allow this?"
> > > 
> > > I was hoping there is an easy fix that doesn't require the use of any other 
> > > libraries (like Redemption), perhaps by changing the way I access the folders 
> > > or mail items, like the "run a script" rule action from the Rules Wizard 
> > > needs to use the EntryID of the VBA procedure's MailItem.
> > > 
> > > 
> > > "Sue Mosher [MVP-Outlook]" wrote:
> > > 
> > >> See http://www.outlookcode.com/d/sec.htm for your options with regard to the "object model guard" security in Outlook 2000 SP2 and later versions. Your Outlook version and the type of application you are creating -- neither of which you mentioned -- are key factors. 
> > >> 
> > >> -- 
> > >> Sue Mosher, Outlook MVP
> > >>    Author of Configuring Microsoft Outlook 2003
> > >>      http://www.turtleflock.com/olconfig/index.htm
> > >>    and Microsoft Outlook Programming - Jumpstart for 
> > >>      Administrators, Power Users, and Developers
> > >>      http://www.outlookcode.com/jumpstart.aspx
> > >>    
> > >> "James B"  wrote in message news:C0F36955-AC32-4089-9ED0-6D69C6795AED@microsoft.com...
> > >> >I have been reading about how to disable the security warning, most suggest 
> > >> > using Redemption, but is it possible to disable the warning by changing a 
> > >> > registry value, or by changing the way base outlook objects are declared?
> > >> > 
> > >> >   Set myOlApp = CreateObject("Outlook.Application")
> > >> >   Set myNameSpace = myOlApp.GetNamespace("MAPI")
> > >> >   Set inbox = myNameSpace.GetDefaultFolder(6)
> > >> >   Set folder = myNameSpace.Folders("Personal Folders").Folders("Inbox")
> > >> >
> > >>
> >

date: Mon, 14 Jul 2008 20:19:01 -0700 author: Jin

Re: disable security warning by accessing different object model

Did you look at http://outlookcode.com/article.aspx?id=52 ?

-- 
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy  - Outlook, CDO
and MAPI Developer Tool
-
"Jin"  wrote in message 
news:DF625708-0D89-48C9-90B8-12589527C3A5@microsoft.com...
> Hi Sue,
>
> I have a macro which is in excel to read other users inbox. I am getting 
> the
> security warning while trying to read the inbox.
>
> Please let me know if there is a way to avoid this warning, when the code 
> is
> not written in outlook
>
> Thanks
>
>
> "James B" wrote:
>
>> omg how easy was that, changed it to this and voila
>> Set myOlApp = Application
>>
>> BTW I found that line in another post of yours lol
>> http://help.lockergnome.com/office/avoid-security-popup-Outlook-2003-ftopict707774.html
>>
>> "Sue Mosher [MVP-Outlook]" wrote:
>>
>> >
>> > Never use a statement like this in Outlook VBA:
>> >
>> >     Set myOlApp = CreateObject("Outlook.Application")
>> >
>> > Instead, derive all your Outlook objects from VBA's instrinics 
>> > Application object.
>> >
>> > -- 
>> > Sue Mosher, Outlook MVP
>> >    Author of Configuring Microsoft Outlook 2003
>> >      http://www.turtleflock.com/olconfig/index.htm
>> >    and Microsoft Outlook Programming - Jumpstart for
>> >      Administrators, Power Users, and Developers
>> >      http://www.outlookcode.com/jumpstart.aspx
>> >
>> > "James B"  wrote in message 
>> > news:965721BF-CCAD-4975-88B8-F66F11249F19@microsoft.com...
>> > > Hello, sorry for the lack of info.  I am using Outlook 2003 on XP 
>> > > with all of
>> > > the latest patches.  My code is VB and saved in a .OTM file (I access 
>> > > it by
>> > > clicking Tools > Macro > Visual Basic Editor from the Outlook menu). 
>> > > I have
>> > > self signed the code and my current security setting is set to High.
>> > >
>> > > I created a function that scans my inbox and puts emails into certain
>> > > folders, bascially just moving emails around.  I then created a 
>> > > shortcut
>> > > button on my toolbar to activate this function.  What I would 
>> > > ultimately like
>> > > to do is disable the security warning that comes up when I click on 
>> > > this
>> > > button, it is the standard warning "A program is trying to access 
>> > > e-mail
>> > > addresses you have stored in Outlook.  Do you want to allow this?"
>> > >
>> > > I was hoping there is an easy fix that doesn't require the use of any 
>> > > other
>> > > libraries (like Redemption), perhaps by changing the way I access the 
>> > > folders
>> > > or mail items, like the "run a script" rule action from the Rules 
>> > > Wizard
>> > > needs to use the EntryID of the VBA procedure's MailItem.
>> > >
>> > >
>> > > "Sue Mosher [MVP-Outlook]" wrote:
>> > >
>> > >> See http://www.outlookcode.com/d/sec.htm for your options with 
>> > >> regard to the "object model guard" security in Outlook 2000 SP2 and 
>> > >> later versions. Your Outlook version and the type of application you 
>> > >> are creating -- neither of which you mentioned -- are key factors.
>> > >>
>> > >> -- 
>> > >> Sue Mosher, Outlook MVP
>> > >>    Author of Configuring Microsoft Outlook 2003
>> > >>      http://www.turtleflock.com/olconfig/index.htm
>> > >>    and Microsoft Outlook Programming - Jumpstart for
>> > >>      Administrators, Power Users, and Developers
>> > >>      http://www.outlookcode.com/jumpstart.aspx
>> > >>
>> > >> "James B"  wrote in message 
>> > >> news:C0F36955-AC32-4089-9ED0-6D69C6795AED@microsoft.com...
>> > >> >I have been reading about how to disable the security warning, most 
>> > >> >suggest
>> > >> > using Redemption, but is it possible to disable the warning by 
>> > >> > changing a
>> > >> > registry value, or by changing the way base outlook objects are 
>> > >> > declared?
>> > >> >
>> > >> >   Set myOlApp = CreateObject("Outlook.Application")
>> > >> >   Set myNameSpace = myOlApp.GetNamespace("MAPI")
>> > >> >   Set inbox = myNameSpace.GetDefaultFolder(6)
>> > >> >   Set folder = myNameSpace.Folders("Personal 
>> > >> > Folders").Folders("Inbox")
>> > >> >
>> > >>
>> >

date: Tue, 15 Jul 2008 10:40:54 -0700 author: Dmitry Streblechenko