Sage 100

 View Only
  • 1.  Now that PU 1 for Version 2017 has been released i

    Posted 02-23-2017 09:15
    Now that PU 1 for Version 2017 has been released is anyone aware of any significant issues that were not fixed with the PU? Any reason to hold off on upgrading customers to 2017 at this point?


  • 2.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 03-07-2017 13:49
    Source Journal drilldown is disabled in Accounts Receivable Invoice History Inquiry after installing Product Update 1 for 2017 https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=82016&sliceId=1&dialogID=307731&cmd=displayKC&docType=kc&noCount=true&stateId=307733&isLoadPublishedVer=&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl


  • 3.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 04-27-2017 09:26
    Although not too surprising, Sage has neglected to update the v2017.1 web page with this HotFix.


  • 4.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 04-27-2017 09:55
    Mixed mode (standard & classic themes) was not addressed since it requires a re-master of the code for the newer interpreter, won't be out until 2018.


  • 5.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 04-27-2017 10:21
    Here's my rolling list-o-oddities http://www.evernote.com/l/AAE4zbCYnS5Nb4c6XNNKZOWf1DL-RuKL9fs/


  • 6.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 04-27-2017 10:34
    Hope you are at a good level right now as it is fixed as of May 1


  • 7.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 04-27-2017 10:36
    Still sounds complex to me


  • 8.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 06-12-2017 11:41
    https://90minds-com.socialcast.com/messages/35864394?ref=stream


  • 9.  RE: Now that PU 1 for Version 2017 has been released i

    Posted 06-12-2017 12:50
      |   view attached
    Installation of 64-bit ODBC driver. KB article claims it's fixed on 2016.2. No mention of 2017.anything. We just ran into it on 2017.1, and used the workaround.

    Attachment(s)