You can experiment with custom components. One that I have tried on rare occasion is dynwrap. You can still get it at G Born's site wsh bazzaar.
It is not easy to use and very restrictive mainly due the datatypes and low-level access script can(not) handle. Note also that it is by no means unique. I do have posted some not immediately trivial tiny use, always for learning and experience on territory not commonly visited by scripter.
However, you can hack into vba using office application. Hence, there you are gaining more freedom as the datatyping is much warmly received.
Here is an example calling kernal function not commonly available to scripting. It illustrates the mechanism of how to do it.
[tt]
dim scode, oxl, owb, omod, idata
scode="declare function GetACP Lib ""kernel32"" () as integer" & vbcrlf
scode=scode & "function acp()" & vbcrlf
scode=scode & "acp=GetACP" & vbcrlf
scode=scode & "end function"
on error resume next
set oxl=createobject("excel.application")
oxl.visible=false
set owb=oxl.workbooks.add
set omod=owb.vbproject.vbcomponents.add(1)
omod.codemodule.addfromstring scode
idata=oxl.run("acp")
set omod=nothing
owb.saved=true
oxl.quit
set oxl=nothing
on error goto 0
wscript.echo "Default/Current ANSI code-page identifier for the system : " & idata
wscript.quit
[/tt]