Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outlook 2003 - No Security Warning

Status
Not open for further replies.

seaport

MIS
Jan 5, 2000
923
US
I was helping a friend on his Access database to create a function to start an email in Outlook 2003. I prepared to explain to him the hassel that he had to deal with the Outlook security warning. But to my surprise, there was no warning on any of his computers (XP, office 2003).

I ask the system administator, who was not clear about that either. He told me something that the Access 2003 had alreay in trust by Outlook 2003.

There are tons of articles on Internet talking about going around this security warning, and I am wondering whether I just ran into a "really simply" solution.

Anyone had the same experience?

Seaport
 
Her probably has the cdo 1.2.1 dll registered on the machine. 1.2.1s is the annoying one with the security popups. Might be worth a peek in the registry, if you're curious.

"No matter what happens, somebody will find a way to take it too seriously."
 
genomon,

I know little about registry. But here is some clue.

The code was simple, like

Code:
with olMsg
    .To=strEmails
    .HTMLBody=strBody
    .Display
end with

Now if i put in .ResolveAll before the Display method, then the warning message appears.

Strangely, at my work place, the code with no "ResolveAll" triggers the warning message.

Seaport
 
Seaport,

The display method doesn't envoke the OL Gaurdian.
.Resolve - .ResolveAll - .Send (and others) will envoke the gaurdian and thus raise the Outlook security warning.

Never knock on Death's door: ring the bell and run away! Death really hates that!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top