1. Dan Cooperstock
  2. PowerBuilder
  3. Saturday, 25 May 2019

We have an internal application for dealing with emails that come in to our Outlook Inbox. It accesses Outlook via connection to the "Outlook.Application" OLEObject, and also uses the Redemption SafeMailItem OLEObject to avoid popups about being allowed to send emails etc.

I'm finding that even though I'm apparently successfully disconnecting and destroying both objects when the program exits, an extra Outlook process is left running, named "MMGA Server (32-bit)". If I keep running and exiting the app, another Outlook process like that is left running each time. Eventually that causes problems.

I can't figure out any way to avoid this. Any thoughts?

One thing I thought of is calling ioleOutlook.Quit(), but that closes the actual Outlook window, that I have no desire to close. (And I don't know whether it even solves the problem.)

Thanks.

Accepted Answer
Dan Cooperstock Accepted Answer Pending Moderation
0
Votes
Undo

This turned out to be something about an incompatibility between Outlook Redemption and the version of Office 365 Outlook I had inadvertently let get installed on a new computer (a Windows Store version, rather than Click To Run, I think), causing all sorts of problems.

One very interesting thing I learned from the very helpful author of Redemption is that in many cases programs accessing Outlook from other apps (like PB apps) will no longer need Outlook Redemption to get around the Safe Scripting permission popups. Apparently current versions of Outlook no longer give those popups requiring permission, as long as you have an up to date anti-virus running! So I have entirely turned off the use of Redemption and everything seems to be fine.

Comment
Thanks for sharing!
  1. Armeen Mazda
  2. Monday, 3 June 2019
There are no comments made yet.
  1. Monday, 3 June 2019
  2. PowerBuilder
  3. # Permalink


There are replies in this question but you are not allowed to view the replies from this question.