We recently upgrade Sage fixed Assets from 2016.1 to 2019.1, today a users reported issues generating reports from Sage 100 2016, that's all the relevant changes that we have made recently.
May Sage could be affected because of this?
We recently upgrade Sage fixed Assets from 2016.1 to 2019.1, today a users reported issues generating reports from Sage 100 2016, that's all the relevant changes that we have made recently.
May Sage could be affected because of this?
Have you searched the knowledgebase for that error? I believe there is a solution listed there for this particular error.
*Community Hub is the new name for Sage City