Scripting

Hello, I'm working on a script to work around the task scheduler bug, to print the general journal and update. So far I'm able to print everything just fine but when it tries to update I'm getting a message that states ""you are not authorized to update the general journal"". Does anyone have any insights (the login I'm using has full rights).

You're using GL_GeneralJournal_upd with SetPostingDate/ValidatePrinter/ProcessReport/UpdateInit/UpdateMain? ODBC Security?

I think I lucked into the solution. see bellow if anyone else is running into this. r = oRpt.nProcessReport(""PREVIEW"") r = oRpt.nupdateINIT() r = oRpt.nupdateMAIN() r = oRpt.nupdateCLEANUP()

Steve actually the script is a modification on the one you posted a few weeks back. (I also managed to get the report you had issues with to post correctly it seems the report options were just slightly off, it works wonders in 2017)

Cool! I've never used UpdateCleanup; does anybody know what that does?

I'm not 100% sure what it does, however when it wasn't there the register ""was interrupted"". The new problem I'm trying to solve is getting Paperless office to initialize using the print command.

As of a few years back, you couldn't do registers (https://90minds-com.socialcast.com/messages/25994129), but maybe you can find a way around it.

Jeremy I took at look at this and I think I got it but I'll let you verify it. This might be helpful also to @JonParkinson and his developer as well when they first reported that this functionality stopped working with v2015 after installing PU5 on top of PU4 (if I remember correct). @SteveIwanowski ran into it as well on the thread he mentioned. I'm sure @DanBurleson has as well. So I got the same ""Unable to initialize "" message like you with the BOI script on the oRpt.ProcessReport(""PRINT"") Then I tried to run equivalent code from SYZCON with ProvideX to make sure it worked correctly there and it did. It processed Paperless correctly. Then via checking of pvx code it led me to Sy_PDFConverter where it looked like after Amyuni DLL was instantiated, it was appearing to fail on the DriverInit() function to ""Sage 100 PDF Converter"". Then saw that prior to that all the _initial_ Paperless properties were being retrieved from the main INI file which is SOTA.INI and from the [Paperless] section. Well everything was there in my SOTA.INI file and that explains why it works form SYZCON, why it works from anywhere inside the Launcher. But only after too much extra troubleshooting, it occurred to me BOI uses pvxcom.exe which uses the PVX.INI in \mas90\home and whaddya know the whole [Paperless] section was missing! So I copied this [Paperless] section from my sota.ini to my pvx.ini based on my v2017 PU2 install and viola the BOI script initializes Paperless correctly and the PDFing works. I see it in the Journal and Register Viewer, etc. But verify all this because my brain tends to circle the drain late at night. [Paperless] Name=Sage 100 ERP Driver==UAlMFOcHU'UUU'UUlc4G]GfAfMuGlRGFuM88U4GOFu]]H'fH4]8GAHFGuFHRMURUlcH'HffOFARUcGll4ucfUAf'4GucMGMR8G8Hl8OuGMuR Printer=Sage 100 PDF Converter Version=5.0

If only my brain worked as well after a full night's sleep and two cups of caffeine as Alnoor's does while circling the drain...

wow Alnoor I would have never found that it works 100% for the register I'll still need to do some testing with other reports though this solves the problem at hand.

I've done some testing with printing sales orders, if you set the DB_Paperlessofficeoutput$ flag to 7 (pdf only), it will still go to the default printer. I suspect there is another call to be made in order to ""trigger"" the paperless print job however I'm drawing a blank for now. I suspect this would be the case for any form that has the drop box for selecting the print style.

Jeremy - Friendly Suggestion: To avoid confusion, start a new thread on this since this subject involves forms instead of journals/registers.