Security Prompt when accessing Task.body Field?

  • Thread starter Thread starter Ryan
  • Start date Start date
R

Ryan

I have a vba that accessing a Task's body field. When the project is
a VBA a do not get the security prompt. I moved it to a COM Add-in
and now I'm getting the security prompt on the Task's body field.
Does anyone know why this is? How can I get around it. Thanks,
 
Thanks Sue but I still have some questions.

1) I get the secrurity prompt when accessingt the body attribute of a
Task only in a COM Add-In. It doesn't come up in VBA. Why?

2) The security prompt says I'm trying to access email addresses. I'm
not just the body of a task.

Is there anyway around this to get and set the body of a task without
the security prompt? I tried using redemptions SafeTaskItem but I'm
not quite sure how it works.

Dim tItem as SafeTaskItem
tItem.item = obj
'tItem.body is blank while obj.body is not, is this right?
 
Outlook version -- did you read the notes on the page I suggested about
Outlook 2003? Code?

The body of a task gets an address book prompt because it can be used to
harvest address information.

Setting the Body property should trigger a prompt at all. It's reading the
property that triggers the prompt. You're on the right track with
Redemption.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Sue I did read your info and I thank you for all the help. But I
couldn't find anything in your info that say's anything about why the
security prompt would only be initiated under a COM Add-in and not in
a VBA. The security prompt doesn't come up in the VBA project but
when I move it to a COM Add-In it does. Did I miss that section,
sometimes I have that problem when something is right infront of me
and I can't see it.
 
This is what I was referring to:

Note that Outlook 2003 by default does not display security prompts in three
specific types of applications:

1) VBScript code in published, non-one-off Outlook forms constructed to
derive all Outlook objects from the intrinsic Application and Item objects

2) Outlook VBA code constructed to derive all Outlook objects from the
intrinsic Application object from the built-in ThisOutlookSession module

3) Outlook COM add-ins properly constructed to derive all objects from the
Application object passed by the OnConnection event


Do all your Outlook objects derive from the Application object passed by
OnConnection?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers



Ryan said:
Sue I did read your info and I thank you for all the help. But I
couldn't find anything in your info that say's anything about why the
security prompt would only be initiated under a COM Add-in and not in
a VBA. The security prompt doesn't come up in the VBA project but
when I move it to a COM Add-In it does. Did I miss that section,
sometimes I have that problem when something is right infront of me
and I can't see it.


"Sue Mosher [MVP-Outlook]" <[email protected]> wrote in message
Outlook version -- did you read the notes on the page I suggested about
Outlook 2003? Code?

The body of a task gets an address book prompt because it can be used to
harvest address information.

Setting the Body property should trigger a prompt at all. It's reading the
property that triggers the prompt. You're on the right track with
Redemption.


regard to
the
Click to expand...
Click to expand...
 
Well i must add that there are some properties exposed by the object model of outlook that are categorized as secure and others non-secure.

Accessing non-secure information like EntryID will not give any prompt, however, accessing any secure property will surely result in security pop-up and a shim, here, can only solve the issue.

The shim actually acts as a mediator between your app and Outlook and makes things easier since all the pop-ups are blocked.
 
Back
Top