Sage 100

 View Only
  • 1.  Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-06-2016 13:05
    Client is running SAGE 100 STD version 5.10PU#7 (v2014). Back in the old days (version 3.71) you could use a ""hidden utility"" called SUMNUA and make changes to the Sage Menu System. As shown in the screen shots below you could change the menu program name and the menu description. How do you do that in v2014?


  • 2.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-06-2016 13:10
    SY_Menu_UI


  • 3.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-06-2016 13:30
      |   view attached
    Thanks @RobertWhite for you input. Yup, the SY_Menu_UI hidden utility looks like it will let me move a menu item and change the menu description. But how do I change the underlying program that the menu item executes?


  • 4.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-06-2016 14:20
    I do not know that but am looking forward to the answer too


  • 5.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-06-2016 22:55
    Michael - I know the answer but what is your specific purpose for changing the program name - is to fix something OR to add a new item to the menu OR something else?


  • 6.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-07-2016 05:11
    @AlnoorCassim My client is running Job Cost v2014. They have a project manager who is an old guy, like me. From time to time he needs to ""Restore"" a single job from history. He uses the Job Cost History Restore Utility - but always restores a wide range of jobs instead of just one. See Selection Screen image below - Panel = JCWSLA. There is a ""Select"" button on this panel that executes Panel = JCWSLB. I want the menu item - Job Cost History Restore Utility to run the Panel = JCWSLB instead of JCWSLA.


  • 7.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-07-2016 21:25
    Thanks for explaining that. Here is the easiest way w/o Dev tools: 1) Make a backup of Sy_Task.m4t, Sy_menu.m4t, and MnuMod.txt 2) Open MnuMod.txt and find Job Cost History Restore Utility. You could do same with Sy_Menu but easier this way. 3) Copy the Task Key that's right next to it into the clipboard except omit the 1st zero. For me it's 180001005 4). DFDM Sy_Task then paste in the Task Key - 180001005 in my case 5) Field 7 ProgramName is the program behind the menu. Note that it's JCWSL2 which is a shell program that launches JCWSLA program and panel. You are lucky ducky that you don't need JCWSL2 modified to load JCWSLB. 6) Edit Field 7 and change to JCWSLB 7) Run Job Cost History Restore Utility. Even if it appears the way you want test it all the way to make sure it works. 8) Since there are no menu changes or additions you do not need to do anything with Sy_Menu or Mnumod.txt. However open a separate DFDM screen anyway and type in Sy_Menu. Field 2 is the same exact Task Key for Sy_Task. Now you know how the menus relate to the tasks. Since 4.00 you cannot have anything on the menu, not even the *UTL stuff, w/o also having an associated Task Key. Also note the field called Checked$. When you use Sy_Menu_UI to hide a menu item it is simply changing the Y to N here instead of deleting the record.


  • 8.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-09-2016 05:57
    @AlnoorCassim I followed your instructions and it Worked! Well almost. I was able to get the menu item changed (see image below). But the program JCWSL2 must be changing the Status from PURGE to RESTORE. (see image below). How can I force the status to RESTORE?


  • 9.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-09-2016 12:49
    No guarantees this will work but you seem to be a lucky guy overall. Once you reach History Selection screen do Ctrl-F9 to open it up in Customizer. Then dbl-click Status field. On the Drop Box Definition [DB_STATUS} screen change the Default Value from Purge to Restore. Give it a go see what happens. In Framework modules this type of thing is done with Advanced Field Settings under UDF Maintenance or with Scripting.


  • 10.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-09-2016 15:28
    Thank my lucky charms (I'm Irish) and @AlnoorCassim. I used Customizer and change the default to Restore. Now it works GREAT! Mega Millions is at 280 million, if I win I will share with you @AlnoorCassim. Thanks!


  • 11.  RE: Client is running SAGE 100 STD version 5.10PU#7 (v

    Posted 06-09-2016 15:57
    I was going to say just send me your Mega Millions picks.