Access/Outlook Automation

[fauxanadu]

Is it possible to run a macro in Outlook from Acces and if so, how (link, explination, or book suggestions)? I've tried MAPI to no avail although i'm open to trying it again with new information.

[NeoPa]

Although I know little to nothing about the Outlook API, you can use Application Automation to control it.

[fauxanadu]

Thank you for the response, NeoPa. However, I've practically written the book on Application Automation^.^ (No seriously... note that I wrote the code in the post you linked too:-)

The problem I am running into is that whenever access attempts to send an e-amil through outlook using an object reference to the outlook application, a dialog box pops up and takes about 4 seconds before it will allow one to click yes to send the e-mail. This happens even if the code is signed with a cirtificate marked as trusted on the computer running the code.

I do not know if it is possible, though, to call a macro in one Office application from another Office application (specifically in Outlook from Access). If this were possible, this limitation could be worked around by calling a macro to send e-mail in Outlook from within Access.

I've tried using the MAPI interface but it just tells me that the macro I am calling doesn't exist within Outlook. I've also tried to write an application in Java that would do the same and I get the same effect.

If this is not possible, I will likely use a program call Express ClickYes that clicks the yes button for the user, but I would prefer a slightly more robust and in-house solution to the problem^.^

[NeoPa]

Ooops :Red Face:

Yes, I had forgotten that the extra code in there was your contribution.

What is it in Outlook that you're trying to call from within Access?

Although I'm utterly ignorant of the Outlook API, I do know that certain things will only work from outside automation when referred to explicitly. That is, when running from the application they're designed for there are shortcuts that you get used to using. When controlling from another application, these shortcuts are typically unavailable so you would need to be more specific in any such references.

[fauxanadu]

One of those aha moments just hit me. I've been trying to write the Outlook VBA in a separate module. The issue is that Outlook treats the module code as external to Outlook itself so one cannot call the macro from within Access or Word or any other application.

However, if you put the code in the default "ThisOutlookSession" module created by Outlook, it is possible to call the vba functions using the MAPI interface.

I cannot take credit for this discovery, however. This page here lead me to the solution should anyone else need to solve this particular problem.

http://www.everythingaccess.com/tuto...curity-Warning

[NeoPa]

That looks pretty handy :) I particularly like the "VBA within Outlook" approach.

Unfortunately, We mostly use Outlook 2000 at work at the moment :(