Timeslips NOT COMPATIBLE with Office 365

SOLVED

This is a known issue and needs to be fixed.  Office 2013 is no longer supported by Microsoft thus REQUIRING users to upgrade to Office 365.  We upgraded only to realize that Timeslips needs a 32 bit Outlook in order to function.  So we uninstalled/reinstalled the 32-bit version hopeing that would fix the problem.  After TWO DAYS of technicians from both our Office products provider AND Sage Support - we find out that Timeslips IS NOT COMPATIBLE with Office 365.  So after days of wasted time - we now are paying a premium price for a product we can no longer utilize for our billing.  We are in a terrible bind and no one at Sage seems to care.  We are told - make a complaint on SageCity - that is all we can do.  There is no known fix at this time and no plans to fix it.  This is simply not acceptable.

We will cease to utilize this product shortly if it cannot be fixed.

Lesa 

Parents
  • +1
    verified answer

    Hi Lesa.  As you know, we have worked with your office and confirmed that the issue you are experiencing is isolated to a damaged computer operating system, and not anything related to a perceived incompatibility with Timeslips and Office 365 (32-bit) software.

    As has been discussed in these forums ad nauseum, Google searches for "Office 32-bit vs. 64-bit" will bring up millions of hits.  The Microsoft website itself gives a precise explanation and the TL;DR explanation is you would use 64-bit when working with massive datasets and 32-bit for the rest of us.  

    Emails are not generally 'massive' with thousands of pages of typed text.  Word documents are not usually the size of the Encyclopedia Brittanica.  Excel spreadsheets not usually the size of the census database for every human being on the planet or since the United States started enumerating citizens.  Some are! And in those cases, yes 64-bit is a requirement.  32-bit works for the rest of us.

    Re-coding an application like Timeslips with many thousands of lines of code from 32-bit to 64-bit is a massive undertaking.  And from the Sage business perspective, it provides near-zero ROI to do so.  For now, that project is not on the immediate future radar.

Reply
  • +1
    verified answer

    Hi Lesa.  As you know, we have worked with your office and confirmed that the issue you are experiencing is isolated to a damaged computer operating system, and not anything related to a perceived incompatibility with Timeslips and Office 365 (32-bit) software.

    As has been discussed in these forums ad nauseum, Google searches for "Office 32-bit vs. 64-bit" will bring up millions of hits.  The Microsoft website itself gives a precise explanation and the TL;DR explanation is you would use 64-bit when working with massive datasets and 32-bit for the rest of us.  

    Emails are not generally 'massive' with thousands of pages of typed text.  Word documents are not usually the size of the Encyclopedia Brittanica.  Excel spreadsheets not usually the size of the census database for every human being on the planet or since the United States started enumerating citizens.  Some are! And in those cases, yes 64-bit is a requirement.  32-bit works for the rest of us.

    Re-coding an application like Timeslips with many thousands of lines of code from 32-bit to 64-bit is a massive undertaking.  And from the Sage business perspective, it provides near-zero ROI to do so.  For now, that project is not on the immediate future radar.

Children
No Data