Sage 100

 View Only
  • 1.  v2016 - Just one of those minor PITA's that can ca

    Posted 01-01-2016 10:30
      |   view attached
    v2016 - Just one of those minor PITA's that can cause MAJOR issues during the first couple weeks of the new year. Remembering to change the module date back to 2015 (e.g. 12/31/15) is a great feature for this date driven software. However, even if you do change the module date, THEN override the default date in invoice entry with (MMDD), the date will return a value of 2016 which appears to be from the system date. Not a major issue unless you are doing a lot of entry work on 1/1/16 and not catch the problem before updating....


  • 2.  RE: v2016 - Just one of those minor PITA's that can ca

    Posted 01-03-2016 14:01
    Yuk, that's going to cause a lot of issues...


  • 3.  RE: v2016 - Just one of those minor PITA's that can ca

    Posted 01-03-2016 14:22
    I think it is a WAD. It has been this way for several versions. I became sensitized to it last year trying to close BLS' books only to find several invoices dated 12/28/16 in the trial balance.


  • 4.  RE: v2016 - Just one of those minor PITA's that can ca

    Posted 01-04-2016 11:43
    Isn't it interesting that in the screen shot you posted, the invoice date is 2016, but the ship date is 2015 ... How about that being WAD????


  • 5.  RE: v2016 - Just one of those minor PITA's that can ca

    Posted 01-04-2016 13:02
    I just love the consistency of the code..... Don't worry about the left hand knowing about the right hand. I don't think the pinky finger knows what the index finger is doing on the SAME hand...


  • 6.  RE: v2016 - Just one of those minor PITA's that can ca

    Posted 01-05-2016 13:25
    Just had a customer call saying she couldn't update her cash receipt as it was stuck in a loop trying to create a new fiscal year. They are not on a calendar year and their fiscal year doesn't end until 3/31/2016 so she couldn't understand why it would be trying to create a new one. While her AR date was 12/31/2015, she entered the deposit date as 12/31 which of course, went to 2016. They only have four periods (quarters) so when I went into Fiscal Year Maintenance, the dates came up correctly except the last one ended on 3/31/16 instead of 3/31/17, thus the loop. They had the same issue last year if I remember correctly. ""Why doesn't it warn you that you are posting to a future year??