Sage 100

 View Only

  • 1.  Sage 100 GL Account Number bugIn GL Detail Repor

    Posted 09-19-2014 06:24
    Sage 100 GL Account Number bug In GL Detail Report, if you type in a any single GL account number without entering the dashes (in ABC for example - 7450004) you will get a message that there is no data selected. But if you type in 745-00-04, data appears. If you type in a range 1000000 through 7600004 (no dashes) with that account included, the data appears. Sage support has confirmed that the problem occurs on their systems also and has turned over to engineering CASE# 8003961951..


  • 2.  RE: Sage 100 GL Account Number bugIn GL Detail Repor

    Posted 09-19-2014 06:25
    version 2014 SP3


  • 3.  RE: Sage 100 GL Account Number bugIn GL Detail Repor

    Posted 09-19-2014 06:42
    As bugs go, it makes sense that it would behave this way. When you enter a range, they are probably doing a >= and <=, and 745-00-04 is included in that range. When you just enter one account, they will do an ""equal to"" for an exact match, and will not find that account. Still a bug and needs to be fixed.


  • 4.  RE: Sage 100 GL Account Number bugIn GL Detail Repor

    Posted 09-19-2014 11:49
    This inconsistency has been happening since day one of the v4.0. Sage's QC sucks. Some GL fields you can skip the dashes, others not!!! Across all modules.


  • 5.  RE: Sage 100 GL Account Number bugIn GL Detail Repor

    Posted 09-19-2014 14:47
    concur with @JeffSchwenk it's not just in v 2014. When Sage made the change to autofill the operand it caused this issue.


Related Content