The printing from older versions is not an issue; the KB article gets us around that issue. My issue is supporting clients on older versions. We do a lot of report and form customization, and most clients aren't ready to upgrade upon release of the new versions. My firm just solved my problem for me, though. I'm getting a new laptop and will retain my older one to continue working with older versions of Sage. Woo Hoo!

The printing from older versions is not an issue; the KB article gets us around that issue. My issue is supporting clients on older versions. We do a lot of report and form customization, and most clients aren't ready to upgrade upon release of the new versions. My firm just solved my problem for me, though. I'm getting a new laptop and will retain my older one to continue working with older versions of Sage. Woo Hoo!

Crystal Reports 2016 is just an updated version of Crystal Reports 2011 - Think of CR 2016 as CR 2011 with an update. 

SAP calls CR 2016 a "Minor" release of CR 2011 which is why you cannot install both CR 2016 and  CR 2011 on same machine. You can only install "Major" releases on same machine. If you want to install CR 2016, you will be forced to first uninstall CR 2011.

"Major" releases include SAP Crystal Reports 2011 (used on Sage 100 versions 2013 & higher), Crystal Reports XI (used on Sage 100 versions 4.4 & 4.5) & Crystal Reports 10 (used on Sage 100 versions 4.10-4.30)

Installing Crystal Reports 2016 Designer is not necessary and you can modify reports on Sage 100 2018 using your existing Crystal Reports 2011.

If you installed the new Crystal Reports 2016 included with Sage 100 2018, you will still be able to edit your reports on Sage 100 2013 & higher

Click the following link for more information found on SAP's website:

https://apps.support.sap.com/sap/support/knowledge/public/en/1216278

Everything Sage100ERPHelper posted seems to be exactly right.

Crystal Reports 2011 is version 14.0.

Crystal Reports 2016 is version 14.2.

Thanks, Scott! Have you tested modifying a report using Crystal 2016 and running it in, say, Sage 100 2015? I'll be able to test it next week if you haven't.

Yes, I successfully modified forms on Sage 100 2015 using Crystal Reports 2016. You still need to add the pvxwin32.exe.config from the 2018 version and place in the ..\mas90\home folder on the 2015 version for it to work on your own installation. If using Advanced or Premium versions, make sure you also include the file in the ..\mas90\home folder that gets created after running wksetup.

If you are modifying forms for your clients, your clients do not need the pvxwin32.exe.config file. You would just replace their .rpt file with your modified .rpt file.

I am trying to upgrade Sage Fixed Assets 2018 on a Terminal Server where we run Sage 100 2016 Premium.   Fixed Assets says it needs to install Crystal Reports 2016 and of course Sage 100 2016 needs Crystal Reports 2011 which is what is currently installed.  My question is: if I uninstall CR 2011 and let Fixed Assets install CR 2016, how will I get the "pvxwin32.exe.config" file to keep my CR 2011 working on Sage 100 2016 since I'm not installing Sage 100 2018 anywhere?   Sorry for the long question.

Hi, In the scenario above you have you will not need pvxwin32.exe.config.  After completing the Fixed Assets upgrade and Crystal Reports 2016 install. Rerun Sage 100 workstation. 

John Nichols

Sage

I installed the Sage Fixed Assets 2018.1 upgrade on two workstations on a network with several other users, all of them, including the two with SFA are running Sage 100 2017. These two users get an "Unable to cast COM" error when running any report in Sage 100. If I try the fix to swap the "pvxwin32.exe.config", the two work but none of the other users do. Rerunning the workstation set up did not fix the problem. 

Pvxwin32.exe.config was created to address Sage 100 2018 and Crystal Reports 2016 runtime compatibility issues.

Copying the file (Pvxwin32.exe.config)from a 2018 installation to a previous release of Sage 100 will also resolve the issue (limitations to only supported versions (2016-2017)).

Could you clarify "but none of the other users do"

Workstations that have not had the Sage Fixed Assets 2018.1 upgrade installed should not be affected  by the version of Crystal Runtime installed by the Fixed Assets client. Crystal Processing is performed on client side except for deferred printing or the System is Terminal services.  

John Nichols

Sage

This didn't work. After completing the Fixed Assets upgrade (there was no separate CR 2016 install) and running Sage 100 Workstation and choosing 'reinstall,' the "unable to cast COM" error occurred whenever printing.

The problem I'm having is there is no MAS90 folder on the local stations. When I tried replacing the pvxwin32.exe.config file on the server with one from a separate installation of Sage 2018, the two that originally had a problem worked fine, but all the other users that didn't have Fixed Assets installed can no longer print anything. So two people can work, or eight people can work, but not all 10.