calling a vbscript from a macro in Outlook 2003

[Mads Remfeldt]

I have a piece of code "Send&Journalize" developed in Outlook 2000,
that is activated from mail. The code journalise the mail in an other
application (Hummingbird - DocsOpen), send the mail and delete it from
Send mail.

The code was developed by a former colleque of mine. To bypass the
security he run SelfCert.exe and signed the code with the certificate.

I tried to do the same thing in Outlook 2003, but with no luck. Outlook
still displays the warning about "An application tries to.....".

I then made a small vbscript "SendKeystrokes" that detect when the
warning occures (the vbscript is places locally on my computer and is
manually activated prior to activating the Send&Journalize) and on
detecting the warning sends the relevant keystrokes.

I have tried to place "SendKeystrokes" code within the
"Send&Journalize"-code, with different errors, so now I am trying to
write a pice of code in outlook vba, that starts the "SendKeystrokes"-
vbscript and then calls the "SendKeystrokes"-sub.

 

[Sue Mosher [MVP-Outlook]]

You're mixing up two different security issues. Signing a VBA code project has nothing to do with the Outlook object model security guard. The issue is probably that your VBA code is not deriving all its Outlook objects from the intrinsic Application object. Fix that and you don't need the kludge. See http://www.outlookcode.com/d/sec.htm

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers