Are you trying to run a BOI script within the Launcher (like a button script on a screen) or outside the Launcher? If within, in the scripting class sample Script 43 quick prints a SO from PO Entry. You can adapt it for that and additional stuff your script needs. Note I recently suggested a few changes to that in my reply to Bob Osborn about that script.
Also BOI always run as Standard, that is "Mas90 Mode". There is no "Advanced Mode" so it shouldn't matter but conflicts can occur if your BOI script uses an object variable reserved for Launcher scripts, like oScript, oSession, oBusObj, etc. That's why in BOI different user defined vars are used like oSS instead of oSession, and oBOIScript instead of oScript.
It appears somewhere earlier in the script you must have:
Set oScript = CreateObject("ProvideX.Script")
Change oScript to either oBOIScript or oPvxScript, then change every oScript reference as well.
Also, make sure you can directly go into GL / Reports/ Trial Balance and can successfully export it the same way with the same report setting and same report options. IOW, if you get an issue/error there fix that then go back to the script.
Also, all BOI scripts "execute on client" so make sure the export path is correct relative to where the script is being executed from.
E.g. if script runs from a workstation then I doubt that D:\Sage\.. path is valid.
Hope that helps.
------------------------------
Alnoor Cassim
Email:
alnoor@asifocus.comPh:
------------------------------