Crystal Report for .NET frame 4.0?  More recent versions of Sage 100 typically use Crystal Report 2012 for Sage.  With the Sage 100 Version 2018 it was just upgraded to Crystal Reports 2016 for Sage.  I would imagine that the underlying run-time dlls are probably different and that is what is causing the issue.  The upgrade probably overwrote the dll's for the .NET version. 

I assume the .NET version came from a different application?  Maybe try reinstalling that version of Crystal?  However, it might mess up reports run under Sage 100 too.

I do know that in the upgrade from to Sage 100 2018,  we are advised to do a few tricks related to Crystal.   Uninstall the 2012 version of Crystal before installing the 2016 version.   Also to copy pvxwin32 from the new Sage 100 2018 into the old installs of Sage 100 2017 and prior (assuming you are still trying to use the old versions simultaneously - which is usually only an issue for Sage Partners - end users not as likely).

What version of Sage 100 were you using previously?   What version did you upgrade to?

Crystal Report for .NET frame 4.0?  More recent versions of Sage 100 typically use Crystal Report 2012 for Sage.  With the Sage 100 Version 2018 it was just upgraded to Crystal Reports 2016 for Sage.  I would imagine that the underlying run-time dlls are probably different and that is what is causing the issue.  The upgrade probably overwrote the dll's for the .NET version. 

I assume the .NET version came from a different application?  Maybe try reinstalling that version of Crystal?  However, it might mess up reports run under Sage 100 too.

I do know that in the upgrade from to Sage 100 2018,  we are advised to do a few tricks related to Crystal.   Uninstall the 2012 version of Crystal before installing the 2016 version.   Also to copy pvxwin32 from the new Sage 100 2018 into the old installs of Sage 100 2017 and prior (assuming you are still trying to use the old versions simultaneously - which is usually only an issue for Sage Partners - end users not as likely).

What version of Sage 100 were you using previously?   What version did you upgrade to?

Thank you Tom,

We are now using the Sage 2017.

The other application is NextGen, is there a way to do a Reg hack to make sure NextGen looks at the version that works for it and then Sage the version that works for it?

And also,

I have uninstalled, Sage from the computer and report works fine, I put it back and it stops. Just wondering if there's a way to make the DLL works for each separately.

I don't really have an answer,  however,  one of my clients uses NextGen and in fact their IT department supports other businesses using it as well.

I don't recall this ever being an issue for them and they are on Sage 100 2017.

I'll put out some queries and see if they ran into this and just didn't mention it and resolved it themselves.

I'm assuming that these reports that stopped working are in the NextGen program,  not Sage 100?

Yes, the filtering stopped working for NextGen and not sage itself. But if I remove sage from the computer it works with no issues.