The limitation with the ActiveX example or using the Windows scripting host application is that you can't use variables that would be set in LabVIEW or return values that would be computed by the script. For self-contained / standalone scripts, it works fine.
Christophe: I don't think that building a full VB parser/compiler is at all something worth spending massive resources on. The Mathscript node requires a lot of attention to keep it up-to-date and to generate good code. I suspect that VB -- a language that gets changes much more frequently than Mathscript -- would require even more attention.
>> I don't think that building a full VB parser/compiler is at all something worth spending massive resources on.
I agree. What if this were implemented like the other script nodes, where it simply interfaces to an external script server? Does such a standalone server exist for VB script?
Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.