Sage 100

I attempted to add PU4 to a clients Sage 100 Standard 2014 test install and had issues that required me to remove the 2014 workstation and reinstall the active system workstation (4.40). Later I tried it on our in house Sage 100 Advanced 2014 system which is not live yet and had no issues and it did not affect our 2013 active install. I learned a few things that I have not seen yet here or at Sage. FWIW, notes are attached. @Sage 100 Routine

Thanks for the notes @JohnBroadfoot

FWIW, more comments. After adding the 2014 workstation to a couple workstations on our in-house system, that 2013 PDF printing started failing on workstations that did not yet have the 2014 workstation. Oh Joy. I ended up using the following steps and they has worked on every workstation I have upgrade so far. First, install the 2014 workstation software and get to work. For me, it usually did. Port was Null which didn't seem to matter, Security on the new Sage 100 PDF converter was OK (I usually added Everyone to make sure it stayed that way) and Registry permissions on the Software folder had held. I am not sure how to tell if a DLL is registered but I did not have to do that so maybe Sage is getting it done now. Second, uninstall the pdf converter, delete the old Sage PDF Converter and reinstall using PL_AdvancedOptions_UI on the 2013 install and go through the usual list to get it working. Third, check both to make sure they are still working. This appears unnecessary as this has worked reliably on all workstations I have updated. On system that have both a SysWOW64 folder and a System32 folder, it still is placing the CDINT500 and the CDINT500_64 DLLs in what I think is the wrong folder. On a system with only the System32 folder , it does put CDINT500 in the System32 folder. Because it works, I haven't messed with it.