Hi just to comment on the bug mentioned in the title: (HIH).
We have the same problem with PB12.6. Not sure if the user is using MAPI or OLE, but for both we solved this problem by "flushing". Since to do so you have to use OLE, MAPI has been discarded by us, except for showing an address list.
The code that does that:
safeoRecip = oleNameSpace.SyncObjects.Item(1)
safeoRecip.Start
------------------- piece of code in which it's being used after the send of the email ----------------------------------------
// trident2, mjl, 11/11/15: flush was missing
if NOT isValid(oleNameSpace) then
if isvalid(safeOutlook_app) then
destroy safeOutlook_app
end if
safeoutlook_app = create oleobject
if safeoutlook_app.ConnectToNewObject("outlook.application") < 0 then
Messagebox('Error', 'Cannot connect to outlook')
// T2, mjl, 19/11/2015: this will happen when having Outlook 2013 opened already and when NOT running the
// executable of the application, with the exe everything goes fine, strangly enough.
of_destroys()
return -1
end if
oleNameSpace = safeoutlook_app.GetNameSpace('MAPI')
// oleNameSpace.Logon('', '', true, false)
oleNameSpace.Logon(gnv_app.is_defaultProfile, '', true, true)
end if
safeoRecip = oleNameSpace.SyncObjects.Item(1)
safeoRecip.Start
/// trident2, mjl, end.
https://www.topwizprogramming.com/freecode_outlook.html
Yes, I've only seen it cause problems for some users who were using Citrix and there was also a time when it failed for the newer versions of Outlook.In that case, we used SendAndReceive instead of SyncObjects. A point worth noting is that many times I have had problems with this kind of stuff and then after some months (=a couple of Outlook updates) problems would disappear without having changed any of my code. Thinking back on Outlook 2013 and 2016. Outlook 365 seems to be a lot more stable.