Richard Kaye wrote:
> After the book, I found the best thing to do is work with the objects at the
> command prompt. The trick with that last one was finding out about the
> GetNameSpace method. After that, I let Intellisense do its thing.
>
> The code snippet I posted does not bring up any security warnings; at least
> on my system. I wrote a number of little VFP automation utilities to create
> folders and update contacts when I was forced by the corporate environment to
> start using Outlook. None of these things caused any security prompts.
> Security comes into play when you try to send email via MAPI through Outlook.
>
> If you want to use MAPI to send mail ("MAPI bad, SMTP Good" - Ted Roche (c)
> 1998?) , I don't think you will be able to work around Outlook's security in
> a standalone environment without using third party tools/hacks. If you are
> working with Exchange 2003 and Outlook 2003, there was a registry hack that
> allowed "simple" MAPI calls to be invoked without Outlook whinging at the
> user. Unfortunately, I figured all that out quite a while ago and don't have
> the details handy.
Craig Boyd's Extended MAPI class gets around the security annoyance
message in OL, iirc.
--
Mike Babcock, MCP
MB Software Solutions, LLC
President, Chief Software Architect
http://mbsoftwaresolutions.com
http://fabmate.com
http://twitter.com/mbabcock16
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/4a952645.5030...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
