Starting with version 4.00 Sage embarked on a multi-year effort to upgrade most of their modules to what they refer to as framework. Within each module upgraded to framework standards Sage modified the underlying data tables, added customizable Crystal Reports to the standard reports menu and made various “under the hood” tweaks to make using Custom Office with the framework module more complete.

Below is a list of Sage 100 modules which have been updated to framework as well as the version that brought the major upgrade. Version releases where no module update was made were typically feature enhancements to the existing modules.

Version 4.0 – General Ledger, Bank Reconciliation
Version 4.05 –
Version 4.10 – Accounts Receivable, Sales Order, RMA
Version 4.20 – Accounts Payable
Version 4.30 –
Version 4.40 – Inventory, Bill of Materials, Purchase Order Processing
Version 2013 –
Version 2014 –
Version 2015 –
Version 2016 –

As of December 2015, the following modules have not made the conversion to framework, though Sage has indicated they intend to consider updates in the future.

Payroll
Work Order
MRP
Job Cost
TimeCard

Here’s a nice solution to a somewhat rare printing problem one of my 90 Minds group members ran into.
The problem appeared in Sage 100 ERP (Formerly Sage ERP MAS 90 and 200) Versions 4.40 and 4.50 versions. These systems both stopped printing ANYTHING from a Business Framework module (forms, reports) and started giving an error 200 in SY_ReportCommon.pvc line 611 in 4.5 and line 596 in 4.4.

Sage says to uninstall and reinstall WKSETUP. Did that. Reinstalled EVERYTHING in 4.4. Including up to PU8.
Here’s what worked:

Via – Alnoor Caassim – Call for Help

It’s trying to create the Crystal runtime object and for BF the main file behind that is CRAXDRT.DLL (the CRPE32.DLL is for legacy). Try to manually register that DLL which is typically in C:\Program Files (x86)\Business Objects\Common\3.5\Bin and the version for it laid down by MAS (as see in properties) is 11.5.something. If you get errors registering the DLL, look for multiple versions of it.

Here Is When Each Sage 100 Modules Was Brought to Framework (Upgraded)

Error 200 in SY_ReportCommon.pvc line 611 in 4.5 and line 596 in 4.4

Contact Us