Sage 100

Upgrading 2013 SQL with cc processing, Sage Exchange v1.0.006.038. I believe that the 2017 data conversion will require the installation of the newer Sage Exchange Desktop 2.0.2. I think this will blow away the current Sage Exchange version. If I uninstall SE 2.0.2 after conversion and then reinstall the original SE, will the current production 2013 install still work. Will the current Vault settings need to be re-entered or will they remain intact?

I believe that v2.0 Desktop will work with v2013. I know for sure it does with v2015. I think you are good without switching back.

Thanks Jeff. What's strange is that I wasn't prompted to install SE 2.0 during conversion. This is the first SQL upgrade that I've done since 2.0 was released. I wonder if the process is different in SQL. I know that a normal ProvideX conversion would prompt or fail if 2.0 wasn't detected.

Sage Exchange Desktop (SED) 2.0 is compatible with the following versions of Sage 100: Sage 100 2017 - in fact, SED 2.0 is required. Sage Exchange Desktop (SED) 2.0 is not compatible with the following versions of Sage 100: Sage 100 2013 - all product updates (5.00.-5.00.9) Sage 100 2014 - all product updates (5.10.0 - 5.10.7) Sage 100 2015 with no product update (5.20.0) Note: For Sage 100 2015.1 or higher, see the Related Resources section (KB 77093) Sage 100 2016 with no product update (5.30.0) Note: For Sage 100 2016.1 or higher, see the Related Resources section (KB 77092) Sage Exchange Desktop (SED) 2.0 is not compatible with the following versions of the Microsoft operating systems: Windows XP Windows Vista Sage Exchange Desktop (SED) 2.0 may not be compatible with third-party enhancements to Sage 100 Note: Some customers have reported error messages with third-party enhancements/programs after uninstalling SED 1.x and installing SED 2.0. **Note: If Sage Exchange Desktop (SED) 2.0 has been installed for an incompatible version of Sage 100, you may uninstall SED 2.0 and install Sage Exchange Desktop 1.x. See the Related Resources section (KB 84681)**

Thanks @WayneShulz