Getting Around Outlook Security

  • Thread starter Thread starter TomT
  • Start date Start date
T

TomT

Quite some time ago, I looked into ways around the
Outlook security warning when a program is trying to
access it (via VVBA). At that time it appeared there was
no way around this, except to use another method to send
mail.

I've moved much of this functionality over to SMTP using
CDOSYS, however there are still some cases where users
want to see and edit Outlook email generated from our
Access front end, and have them in their Sent Items.

I was wondering if there currently exists a way to
disable the security warning, in, e.g. Outlook 2002 or
2003, perhaps by digital signatures and certificates.
Users are living with the warning, but don't like it
much. We actually delayed applying service paks to
Outlook 2000 to avoid the issue, but have had to finally
give in and apply them.

Any help would be greatly appreciated.

Thanks
 
According to Outlook MVP Sue Mosher:

" ... Outlook 2003 does not show security prompts on three specific types of
applications:

-- VBScript code in published, non-oneoff Outlook forms

-- Outlook VBA code that uses the intrinsic Application object

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

For more details, see her WebSite:
http://www.slipstick.com/outlook/esecup.htm#autosec.
 
Cheryl,

Thanks very much for your reply. I checked the site you
mentioned, but (and I may be getting old and blind) I
didn't see any references to Outlook 2003.

Could you elaborate, please on the second type you
mentioned "Outlook VBA code that uses the intrinsic
Application object"?

Thanks for your kind assistance.
 
didn't see any references to Outlook 2003

http://www.slipstick.com/outlook/ol2003.htm discusses Outlook 2003 and has
numerous links to sub-topics.

Could you elaborate, please on the second type you
mentioned "Outlook VBA code that uses the intrinsic
Application object"?
Click to expand...

As mentioned in my reponse to your question, that is a quote from Sue in a
response to post(s) in one of the Outlook newsgroups. However, my
interpretation: it just means creating an application object via VBA, after
which all of that object's properties, methods, items, etc., are available
for your use. See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbaol10/htm
l/olobjApplication.asp
 
Well it's certainly no easier in A2002. Redemption or ExpressClickYes are
still the standard ways through.

As I understand it, without testing A2003, things are still the same for
anybody trying to automate Outlook from another product (Access/Excel
etc). The concession is that you can write code within Outlook that
doesn't trigger the alerts.

I believe MS have said things will not change for other apps because of
security issues.

Regards

Peter Russell
 
Many thanks. I read that article to mean that using VBA
in an Access front end to open and otherwise manipulate
Outlook 2003 messages (as I'm doing now, but against
Outlook 2k), the user will no longer get the security
prompt.

Is this correct?
 
Hi Tom,
No, any VBA code that tries to manipulate Outlook from
another program will generate the prompt:

"Users, however, continue to get Outlook security prompts in VBA code in Microsoft Word
, Excel, and other Office 2003 programs and in any programs external to Outlook that
use Outlook programming objects"
 
Forgot to mention, as Peter says, Redemption is the way to go.
I've used it and it only takes slight modifications to your existing code
to work with it. It completely eliminates the security prompts.

Google on: Outlook redemption
 
Back
Top