Working on an upgrade from Sage 100 Standard 2013 with DSD's precision mask (CIDP), ACS MB, and MAPADOC to 2019.
After getting the source install cleaned up and prepared (lots of issues during first few rounds of attempted migration and conversion), the post migrated and converted install displays the "J/C not on file" message when attempting to start numerous entry tasks in several modules, Sales Order Entry, SO Invoice Data Entry, Purchase Order Entry, and AR Invoice Data Entry are a few examples, now usually this message is a red herring and just a warning but that doesn't seem to be the case here.
I followed Scanco's instructions for installing MB for 2019.2.
I have tried renaming the links folder.
I have tried disabling customizations using *ESC.
I have unchecked allow external access.
I have tried copying the following folders from a clean copy of 2019.2 with the mods installed and from a 2019.2 copy without the mods installed to rule out program class changes and system files. This process consisted of renaming the folder in the problem instance and then copying one folder at a time from the clean install and then starting the workstation and trying to access the task. I repeated this until all of the following folders had been copied over.
- AR
- CI
- GL
- Home
- Launcher
- Links
- MAS_ABC
- MAS_XYZ
- MAS_System
- PO
- SO
- SOA
- SY
I have verified in DFDM that in each of the applicable modules' options file, IntegrateJobCost is equal to "N" as well as using the options task from the menu to confirm this.
The message does not appear in the clean installs with ABC or XYZ demo data, even with the mods installed.
The message will only go way if I copy providex.ddf and providex.dde from the clean install with mods to the problem install. So this leads me to believe that somewhere, even a stock sage 100 program is reading the physical file incorrectly and grabbing a "y" value from a column and thinking it is the IntegrateJobCost column. I have not figured out which program or options file is causing this.
I'm thinking I might be able to export UDFs and UDTs from the problem install so the export is at the required 2019 version, then copy over the providex.ddf and providex.dde files from the clean install with mods, import the UDFs and UDTs, and then use SYZCON to activate every module but not 100% sure this will work.
Final issue is that with the DSD mod (that i'm aware of atm), when a decimal precision is set in CI Options beyond the standard 4 decimals, i get this error in Work Order Entry in 2019.2 but not in the 2013 install. I i set the precision back to 4 or less, the error goes away.
Any insight/ideas are appreciated
EDIT:
If I install JC, the message changes to JC_Options not existing. If I manually create JC_Options using Reinitialize Data Files, the message changes to saying the key does not exist. So I believe this is not just a red herring and sage really thinks JC is integrated when its not.
#Upgrade #Sage100
#mods
------------------------------
David Speck II
Tennessee Software Solutions
------------------------------