Sage 100

Just spoke to an orphaned Sage user that has Job*Ops on a 4.40 install and stopped using it several years ago and now wants to upgrade to 2016, without JOB*OPS. Any thoughts on uninstalling JOB*OPS on 440, or moving to 2016 and not installing JOB*OPS, etc.

I just completed this for a 4.3 to 2016C upgrade, you have to remove JobOps or 2016 will not let you migrate the data. Below are the instructions. The end user also needs to be aware that by doing this process, they will no longer have access to any JobOps data that was created. MAKE SURE TO HAVE A BACKUP OF MAS90 - Launch Sage MAS 90 / 200. 1. Remove the JobOps data from all companies - This is performed from Company Maintenance 2. Uninstall the J/T JobOps module from System Configuration (Uninstall button) 3. Manually reinitialize the SY_ClassEnhancement.M4T file of the JT158 records 4. From windows explorer - access the MAS_SYSTEM directory and remove the SY_158JobOps file (this holds JobOps Reg Keys and is not removed) 5. From windows explorer remove any JTxxx directories - these sometimes linger 6. From SY_Enhancement remove reference to JT or 158 7. From SY_Module remove JT Module - Install all Sage MAS 90 / 200 modules and any other custom enhancements/customizations into the current directory where MAS is installed. Doing the reinstallation of MAS puts all programs back to standard MAS. The SO Data files do not get reformatted to Standard MAS90. If this is an issue you can manually review the files in the data dictionary and remove fields referencing 158. You do not need to convert the data. Run the Custom Office utilities. NOTE\ADDITION: If they have no other 3rd Party installed in the Links directory remove everything except default.pvc. Run workstation setup again to each workstation to reformat the menus.

@LisaDion - Perfect. Thanks!!

Thanks Lisa - Great list, I'm going to keep that handy. I want to point out one thing though: **Manually reinitialize the SY_ClassEnhancement.M4T file of the JT158 records** that is a little confusing; you would want to use DFDM to manually remove the JT158 Records from SY_ClassEnhancement.M4T - A manual re-initialization would remove all enhancement records not just job ops. there are a couple of other tables where enhancement records could be stored. SY_Enhancment and SY_enhancementModule come to mind. The Job Ops instructions might not need to mention these if the uninstall process cleans them out.