Bug 3506

extended mapi behaviour has changed between PB 12.6 and 2017 and Outlook 365 / 2016 05 February, 2020

Miguel Leeuwe
21 October, 2019
Product: PowerBuilder Category: PowerScript
Version: 2017 R3 Build:
Classification: Publishing: Public
Priority: P3
Status: Closed Reason: RESOLVED
Miguel Leeuwe 05 February, 2020
I have made a new bug: 4032. I now realized I CAN still reproduce the bug. Sorry for any confusion.
Ken Guo @Appeon 04 February, 2020
Hi Miguel,

Glad to hear that. We will close this ticket! 
If you have any further question, please open a new ticket.

Miguel Leeuwe 03 February, 2020
When looking at another bug, I tried to reproduce this problem:
It no longer fails the way it did before, so either office 365 has done a fix or the latest MR fix on pb2017 r3 has fixed the problem.
This issue can be closed as far as I'm concerned.
Miguel Leeuwe 22 October, 2019
Thank you,
Remember that Outlook must be CLOSED before testing from the PB IDE. When running the executable, it makes no difference if Outlook is already open or not.
Ken Guo @Appeon 22 October, 2019
Hi Miguel,

I'm working on analyzing it. I will keep you posted of the results here.

Miguel Leeuwe 21 October, 2019
My excuses, I made a mistake:
The line 
"When you set it to Yes, it'll all work, which is contrary to PB12.6."
should be
"When you set it to No, it'll all work, which is contrary to PB12.6."
Miguel Leeuwe 21 October, 2019
We use MAPI to popup an address list of emails of Outlook 2016 (I think everything was ok with previous versions, but not sure).
The problem is that it does not work wel when in you PB.INI your setting is UseSimpeMapi=Yes.
It has to be 'No' now for some reason.
If not, when doubleclicking on an address in the list, the address is preceded with a "; " (only the first time you do that) and the address does not evaluate as "resolved correctly" when using ResolveAll() on the recipients.
To reproduce the problem on PB 2017, use Office 365 32 bit, Outlook 2016, and the following setting in the PB.ini:

When you set it to Yes, it'll all work, which is contrary to PB12.6.

*Reproduce Steps:
You can download a test application from 

The failing "resolve" happens in line 36 - 43 in the object u_email and object function of_recipients_resolveall_mapi_outlook(), which is activated after using the "TO:" button.

Maybe it's not a bug, but just a changed behaviour, but it means that the many times adverted solution of setting this to Yes, no longer works for PB2017 if you want to use Mapi resolve recipients.
Windows 10
Database Type:
Database Version: