Based on my experience, one has to modify the XML file of the application that interacts with the Crystal Report runtime to ensure it retrieves the correct information version. If you don't have control over the XML file, this can become challenging and time consuming.

A practical workaround that can save you a significant amount of time is to download the Crystal Report runtime specifically for Visual Studio for applications. This installation will occur alongside the standard Crystal Report runtime. By doing this, you can run your application using its own runtime while Sage continues to operate with its originally installed version, thereby avoiding installation conflicts and cross overs.

I’ve found this approach to be quicker and more efficient than constantly trying to synchronize different Crystal Report runtimes, especially when dealing with older versions that may not be readily available.