bradbeckett1
Active Member
I have to loaded large ESU for payroll, several of my applications in payroll are slightly modified (time entry etc).
I installed the ESU .exe on my Dep server, logged into JDEPLAN and updated my Dev enviroment. Built and installed a full package and now in Dev all custom mods are gone.
From the Dep server if I looked at Merge Specs (p98401) from the DV, PY, PD, or DEP7334 I see all my modded programs correctly marked as "C" changed with spec merge set to "1".
If I log into JDEPLAN and look at P98401 I don't see any of my programs marked as "C" with merge code "1" set.
JDEPLAN has the object lib ODBC pointed to a local MDB file. DEV/DEP/PY/PD are all pointed at my SQL server, hence the differences.
I've RTF esu manual twice, and it's specific about running the ESU workbench from JDEPLAN.
So is my configuration mucked up and JDEPLAN should point at my SQL box for Object Lib so it can see the correct merge specs? I did run the backup during my ESU install so I can roll that back (and I have sql and dep backups worst case).
Just trying to figure out if I missed a step during the ESU or if the consultant that installed my dep server mucked up something during the install.
TIA
Brad
I installed the ESU .exe on my Dep server, logged into JDEPLAN and updated my Dev enviroment. Built and installed a full package and now in Dev all custom mods are gone.
From the Dep server if I looked at Merge Specs (p98401) from the DV, PY, PD, or DEP7334 I see all my modded programs correctly marked as "C" changed with spec merge set to "1".
If I log into JDEPLAN and look at P98401 I don't see any of my programs marked as "C" with merge code "1" set.
JDEPLAN has the object lib ODBC pointed to a local MDB file. DEV/DEP/PY/PD are all pointed at my SQL server, hence the differences.
I've RTF esu manual twice, and it's specific about running the ESU workbench from JDEPLAN.
So is my configuration mucked up and JDEPLAN should point at my SQL box for Object Lib so it can see the correct merge specs? I did run the backup during my ESU install so I can roll that back (and I have sql and dep backups worst case).
Just trying to figure out if I missed a step during the ESU or if the consultant that installed my dep server mucked up something during the install.
TIA
Brad