I'm not sure if the thread title is the explicit request (using Interop.Call) or if it is because he didn't know you can make and use ActiveXs yourself too. So to answer people who read this thread and would otherwise be misinformed:
quote:
Originally posted by Matty
If you are using Visual Basic you need to use a tool called VBAdvance so that it will export functions other then that a standard Windows DLL with Functions Exported would be fine.
You don't need that (not free, and not available anymore) tool since in VB you can make an ActiveX OCX or DLL nativly and since it is ActiveX it can work in scripts too.
Anyways, the tool vbAdvance can indeed make standard DLLs, but there are a lot of caveats and requirements and limitations. And if one isn't an extremely advanced VB programmer and if one doesn't have expert notion of APIs aand other advanced programming techniques it is even suggested in that tool itself to not even attempt it.
quote:
Originally posted by afelipE_scripts
you should create the DLL as W32 DLL, not activeX. or trying create activeX dll?
No, an ActiveX can work in scripts too. Heck, extremely many scripts use ActiveX objects, if it weren't for ActiveX half the existing scripts wouldn't work.
/ 
