The Script Control object could not be created


Posting this in case it helps someone else.  Client is on SPC (new), v2022.2, and we received this error when trying to add a UDS (clicking the green check-mark button to verify syntax).

The script host was properly installed (and Allow External Access enabled), with correct file association, but it turns out they were running the 64-bit version of Sage 100.

Changing to 32-bit (running the utility) fixed the error.

Parents Reply
  • 0 in reply to scmember

    "COM / OLE is 32 bit." - That statement is incorrect.

    The original question/issue stemmed from our Script Host component not getting registered properly and is something we are looking into. As to your question, it was previously answered; Scripting (COM/OLE) is supported using Sage 100 x64. In this scenario, the full COM component stack is x64 down to the language libraries. Note: Microsoft provides both x86 and x64 scripting language libraries (vbscript.dll/jscript9.dll), which can be found in Windows\SysWOW64 and Windows\System32 respectively.

  • 0 in reply to Russell Libby

    It seems 64 bit COM/OLE is a small world with only VBA and JavaScript supporting it. It doesn't look promising for C# and OLEDB for 64 bit seems to have issues and not recommended. Would moving to .NET be a rewrite? I've seen 64 bit apps calling 32 bit COM objects. My vote for 64 bit ProvideX would be supporting 32 bit COM as an option.

    Will 32 bit ProvideX be around for awhile?