Scripting

Has anyone else been able to use nProcessReport(""Print"") successfully from an external BOI script on v2018? I'm getting the attached error and from what i can tell, it has to do with crystal reports runtime components.

Solution is to copy pvxwin32.exe.config to all locations where pvxcom.exe exists and rename to pvxcom.exe.config.

seems like you have that one, but i figured this from last year falls in line with this thread, in case someone is trying to use paperless office. Per Alnoor Cassim 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

Yeah, i remember that thread, it solved a previously unresolved issue that i had posted to sage city 2 years ago. https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-business-object-interface/100903/unable-to-use-paperless-office-from-an-external-boi-script-yet-the-same-script-will-work-when-launched-from-a-button-or-table-script Just realized it never got an answer so i just posted the solution.