Why VBRun is better than VBEval

General Macro Scheduler discussion

Moderators: Dorian (MJT support), JRL

Post Reply
OlgaFB
Pro Scripter
Posts: 58
Joined: Mon Nov 01, 2004 3:04 pm
Contact:

Why VBRun is better than VBEval

Post by OlgaFB » Fri Aug 04, 2006 3:13 pm

Hi all,

From a long experience: :)

when you need to get something from VBS, if it needs some input parameters, don't use functions in VBS but procedures.

Why: because when you pass as a parameter a string that contains quotes or comma or some other special characters, then it all will be interpreted as a statement in VBS instead of passing as one parameter. A good example is when you need to give as an input a file text that you can't be quite sure what it may contain.

For this you're welcome to use the technique I give the code for here (code, defining and using GlobalReturnStr).

Happy coding! :)
Olga.

OlgaFB
Pro Scripter
Posts: 58
Joined: Mon Nov 01, 2004 3:04 pm
Contact:

Post by OlgaFB » Fri Aug 04, 2006 3:16 pm

I meant calling functions/procedures and passing parameters between Macro Scheduler and VBS, not inside VBS.

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts