Sage 100

 View Only
  • 1.  I am having a spate of clients, all on Sage 100 St

    Posted 10-23-2015 12:55
    I am having a spate of clients, all on Sage 100 Standard (either 2013 or 2015) complaining about slowness. Besides AV, and, of course, hardware (mostly switch speed?), is there anything that seems to be an issue with the more recent versions? Two who are on 2015 have lockups, not just slowness. I've searched everything on Sage's website pertaining to slowness and sent it to their IT folks, but no love yet.


  • 2.  RE: I am having a spate of clients, all on Sage 100 St

    Posted 10-23-2015 13:04
    I just upgraded a client from Sage 100 2014 Standard to Sage 100 2015 Advance earlier this week. They are seeing NO SPEED enhancement at all. They have 12 years of history. I was hoping they would see some type of speed improvement. Big disappointment.


  • 3.  RE: I am having a spate of clients, all on Sage 100 St

    Posted 10-23-2015 13:11
    YIKES!


  • 4.  RE: I am having a spate of clients, all on Sage 100 St

    Posted 10-23-2015 13:41
    @MadelineStefanou - What do you mean by speed enhancement? Processing transaction update - You should see them but this is dependent on the server processor speed, memory, user counts, etc. If you are referring to Crystal or SI report generation then you will not see any uptick in speed here unless you have activated the CS ODBC service as ALL crystal processing happens at the workstation other wise. The way I demonstrate the difference STD and ADV before selling them ADV is to run a report or big update (SO end of day or PR calc report) at the workstation then I do the same from the server console. I did this once for a client. PR calc took 65 minutes from the workstation and only 5 minutes from the server console.


  • 5.  RE: I am having a spate of clients, all on Sage 100 St

    Posted 10-26-2015 08:54
    I have a client with speed issues in everything. Screen changes, printing reports, posting. Tried all the Sage suggestions to no avail. They have had the issue in both 2014 and 2015.