cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Outlook 2016 and TC12

Contributor

Re: Problem with Outlook 2016 and TC12

Obviously, with Outlook 2016, there cannot be more than one instance of Outlook. Maybe there is an option in the windows registry to retrieve the old behavior.

Community Hero

Re: Problem with Outlook 2016 and TC12

Hi,

 

The problem of the Sys.OleObject() and solution recipe for Excel can be found here: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Get-COM-reference-for-a-running-Excel-ins...

 

Hopefully, you will be able to find similar objects for Outlook and implement the same approach for it.

If you do, I think that a lot of people will appreciate it if you mention your findings here...

Regards,
Alex
[Community Expert Group]
____
[Community Expert Group] members are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Postings made by [Community Expert Group] members
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
[Community Expert Group] signature is used with permission by SmartBear Software.
http://smartbear.com/forums/f83/t86934/community-experts/
================================
Contributor

Re: Problem with Outlook 2016 and TC12

The solution I came up with is to look to see if outlook is running and if it is close it before making the connection. So far this seems to work.

 

    var OutLookProcess = Sys.WaitProcess("outlook",2000);
    if(OutLookProcess.Exists)
    {
      OutLookProcess.Close();
      aqUtils.Delay(2000);//Give time to close Outlook
    }
    var OutlookApplication = Sys.OleObject("Outlook.Application");

New Here?
Join us and watch the welcome video: