Sage 100

The Sage 100 KB , in my opinion, is on a permanent decline.

It is unlikely to ever get any better and the retention and improvement of Sage 100 knowledge should be moving up several spots on the 90 Minds "mission list".

• It is all but impossible to get a complete set of install disks - which includes needed patches - from the Sage download library.
  • For example, Payroll 2.25 doesn't include ANY links to interim patches which might be required by some users.
    • Well, I guess Payroll isn't that time sensitive so let the end user debug and spot the error. Then the VAR is left scrambling to search first the KB then the Download KB ( yes, if you haven't noticed Sage has two separate KB to search )
• Sage for the most part no longer issues one-off patches in the Download library. In many cases if you need a fix before the PU then you are asked to sign an agreement on behalf of your end user ( hello liability ).
• The KB articles rarely ( if ever ) make mention of what version an issue was reported at. So it's difficult/impossible to proactively notify end users that an issue was found that might apply to their version and perhaps we should apply a patch.
• Sage doesn't appear to have any game plan for 32 to 64-bit upgrades when that requirement hits reportedly in 2026. In fact, Sage hasn't even kept up the KB for relatively new behavior for the service account which apparently began with v2024 (see Russell Libby comment)
  • A game plan that involves
    • "Just get a new server"
    • "Login as the Domain Admin" or use a Domain Admin account for anything
    • Run the 32 to 64-bit conversion if you are on Windows 11 because Sage can't or won't fix an issue
    • Is no game plan at all - it's "rear view mirror" support - the minimum effort to fix something that rightfully belongs on Sage's plate
• The support around Sage 100 Premium for FAQ type questions which are not overly technical has been very poor in the past. End users typically have several questions about SQL that the Supported platforms doesn't address. Sorry but I'm tired of repeating "if it's not on the SPM then it's not supported" for newer technology that Sage just hasn't gotten around to testing.

As Gary Feldman said in one of his sessions - anytime you're going to complain come with a suggestion on how to make things better.

1. I don't believe we can rely on Sage to reinvest in knowledge
2. As a group we need to pick up the slack - complaining to Sage doesn't work and Sage is primarily interested in quick fixes at this stage in the product lifespan
3. This only works if we are all collectively proactively sharing knowledge
4. As I said at the consultant roundtable - make 90 Minds your first stop to share knowledge when you discover an issue (and possibly a solution) that could help another 90 Minder. You will not be asked to spend time formalizing the solution and writing it up (unless you want to then please do join our 90 Minds Library committee)
5. In the 1990s when this group was first started it was "US against the big VARS". Those days are gone. Now, IMO, it's "US against the decline in Sage 100 knowledge"
6. We, as a group, have a wealth of experience. By proactively sharing what works and what doesn't, and by documenting this knowledge, we build a stronger foundation for our group and more importantly our end users who rely on us for support. We can't solely rely on external sources to capture the nuances of our work. Let's make knowledge sharing a priority!
   
   
   

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
CT
------------------------------