Hey, don't know of any changes in terms of the Outlook compatibility but the specs for the 2016 product haven't been released yet so it is hard to say. Best bet to get this addressed is to go to Help-Contact Sage-Give Us Your Feedback, can do this in any company file. It goes to the dev team and it is really valuable to us in terms of moving the software forward. The more they hear about something the more likely it is to be addressed, or that feature added in.

Thank you for your comments, Erik

Erik79 said:

the specs for the 2016 product haven't been released yet

It's a bug fix.  Yeah, Microsoft made a change that broke it, but they're not changing it back.

Erik79 said:

The more they hear about something the more likely it is to be addressed, or that feature added in.

Sage has created several tech documents to explain when it doesn't work.  You seem to be suggesting that they just need to hear more complaints?  I suppose 'Should Emailing work? with Office 365' could be put to a vote on Ideascale. 

The Ideascale site seems to be more wishing well than communication tool.   

Is Sage pre-filtering these items?  Why not just "throw it at the wall and see what sticks?". 

In the above case, if the 'real answer' is (for whatever reason), there will never be any new 'canned' reports, or fixes to old ones, it would be helpful if Sage would just... say... something. 

Or there's really no conversation.

Hey, for the idea scale thing there should be no filtering, defeats its purpose for us as a tool for the dev team. If you are having issues with things you are posting there not working properly then please call in at 888-522-2722 or 888-222-8985

Erik79 said:

Hey, for the idea scale thing there should be no filtering

???  The items that are posted are first vetted by someone at Sage, before anyone on this side of the firewall other than the poster can see them.   The process seems to take about a year. 

Erik79 said:

If you are having issues with things you are posting there not working properly then please call in

I think you wildly overestimate the strength of my commitment to helping Sage, or any other vendor.  It's not even always above the 'I told you once' level.   It's rarely been up to the level of  'I'll spend an hour navigating a vendor's voicemail system to find the person responsible for maintaining their website.'

Erik79 said:

Hey, for the idea scale thing there should be no filtering

???  The items that are posted are first vetted by someone at Sage, before anyone on this side of the firewall other than the poster can see them.   The process seems to take about a year. 

Erik79 said:

If you are having issues with things you are posting there not working properly then please call in

I think you wildly overestimate the strength of my commitment to helping Sage, or any other vendor.  It's not even always above the 'I told you once' level.   It's rarely been up to the level of  'I'll spend an hour navigating a vendor's voicemail system to find the person responsible for maintaining their website.'

For problems Emailing from Windows 64 bit, and 32 bit office, this registry key may not have been created during installation of Office 2013 or Office 2016:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Messaging Subsystem]

"MAPI"="1"

** warning, changing registry settings can affect your computer **

** More importantly, Driving in winter on 'all-season' radials can cause serious problems **

We had trouble with 8 of 10 machines where Office 2007 was previously installed, and upgraded to Office 2013. 

Office 2013 worked fine on 2 workstations where the user account used for the installation did not have local 'administrator' rights.  Something Goes Wrong with the legacy email settings, so Sage 50 never attempted to load the MAPI32.DLL from c:\windows\SysWOW64. 

The resulting error message when trying to Email from the afflicted systems was 

"Sage 50 cannot communicate with your e-mail program.  Please ensure that your e-mail program is MAPI-compatible and that it is the default MAPI client."

Outlook 2013 is definitely MAPI-Compatible, and it was the default client.  Testing with one of Sage's competitor's software on the non-working system showed that other accounting software could send e-mail, but none of the versions of Sage 50 that once could send e-mail, would work.  

I finally printed out the list of DLLs from Help | About | Support Info and compared the working / non-working sytems.  The non-working systems didn't have MAPI32.DLL loaded.  

Now that I knew that the issue happened at startup, instead of when Emailing, another few runs with SysInternals' program PROCMON gave the final clue.  On 64 bit workstations, Windows only shows 32 bit applications the 'WOW6432Node' 32 bit registry keys, since they're running inside a 32 bit emulator, on 64 bit Windows.   It's the same sort of thing that we would run into back in the Windows 3.1 / windows 95 days, only instead of 16 bit / 32 bit, now it was 32 bit / 64 bit. 

Once the missing registry key was exported from one of the 'working' units and imported to the 'non-working' ones, the issue was resolved.

I hope the above helps anyone who has been getting that error message.   The only outside help (Sage 50, Microsoft, a local consultant) we ever were able to get seemed focused on fixing blame, not fixing computer software.  

Randy