If you are a Sage 100 partner or user that uses Custom Office with BOI (Business Object Interface) scripts that are written in Microsoft VBScript to Interface with ProvideX via a COM interface, take note.
Microsoft has deprecated VBScript in WSH (Windows Shell Host) which is an optional install on Windows 11 and to be removed in 2027 is the plan. VBScript: Officially deprecated by Microsoft as of October 2023. It is largely being replaced by Windows PowerShell for administrative tasks.
ScriptBasic is an embeddable traditional BASIC scripting engine written in ANSI C with a 800 KB footprint. It supports COM to Interface with Sage 100 BOI. I have been using ScriptBasic for years for external BOI interfaces for clients.
Sage 100 currently supports WSH and ProvideX as scripting options. I'm in the process of adding ScriptBasic as an option. ScriptBasic COM is line for line equivalent to VBScript. I plan to write a script to convert VBScript code to ScriptBasic COM.
An added advantage of using ScriptBasic is beside COM support, you can make REST calls from your BOI scripts directly. ODBC, MySQL, SQLite and other extension modules are also available from within ScriptBasic.
The memory footprint for PowerShell typically starts around 30 MB to 100 MB for an idle session, but can quickly scale into the gigabytes depending on the scripts and data being processed. Because it is built on the .NET framework, it uses a managed memory model where memory is allocated and released through a garbage collector.
Windows Script Host (WSH) typically running via wscript.exe or cscript.exe is known for having a very low, lightweight memory footprint, often occupying only a few megabytes of RAM for simple scripts.