Sage 100

 View Only

  • 1.  Paperless Office Output Setting

    Posted 05-19-2021 20:37
      |   view attached
    When in the Printing selection window of any form, the setting that is last chosen for the Paperless Office Output does not save by user key or workstation.  I've had many customers complain about this.  While it is great that the SY_LastFormUsed file exists so Sage at least keeps track the Form Code by user key, I can't find anything that saves the paperless output setting - can't even find the file that holds this setting.

    Is it just me, or shouldn't this setting be part of LastFormUsed? 


    ------------------------------
    Jane Scanlan
    Partner, Next Level Manufacturing Consulting Group
    Next Level Manufacturing Consulting Group
    Chanhassen MN
    952-210-7758
    ------------------------------


  • 2.  RE: Paperless Office Output Setting

    Posted 05-20-2021 07:18
    I like this idea too.

    I wonder if there is a reason Sage didn’t incorporate this ability

    ---------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ---------------------------------





  • 3.  RE: Paperless Office Output Setting

    Posted 05-20-2021 14:26
    It is saved by module, company, task, and form code in SY_ReportOption.  It is contained in the "OptionString$" field which is a semi-colon delimited string of all the options for that task.  So it isn't exactly by user and workstation as one user's last used options will be saved and the next user to use that form will see those settings loaded as default.  IIRC though, only form codes that are not "STANDARD" will have the options saved.

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 4.  RE: Paperless Office Output Setting

    Posted 05-20-2021 14:30
    Also, as long as a UI post load script can be attached to the panel, you can use logic to set the options to specific values, however, doing this initially only affects the form loaded when the task loads the last form used, if they were to change the form code to something else, Sage 100's logic takes over at that point, if you also need to trigger your logic on the change of the form code, it is necessary to append your own logic (easiest to do with another file containing all of the perform logic) to the controls change event.

    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------

    Original Message


Related Content