VBScript has two types of arguments... Named and Anonymous and they are provided as follows:

C:> cscript.exe /nologo script.vbs /CycleDate:01-12-2005 /Test:2 Arg1 
+Arg2 Arg3
[download]

This results in three Collection Objects Arguments(), Arguments.Named() and Arguments.UnNamed()

These will have elements

'VBScript, not Perl
Arguments.Named("CycleDate") 'value="1-12-2005"
Arguments.Named("Test") 'value="2"
[download]

There should be three elements of Arguments.UnNamed() with values "Arg1", "Arg2" and "Arg3".

Documented at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/wslrfnamedproperty.asp

If you're converting you might use Getopt::Long - then you'd have GetOptions( "CycleDate"=>\$cycledate ...) or warn...

HTH -- Mark

When I am converting code from one language to another (which I thankfully don't need to do now - that was a student job I had back in 1993 - converting ForTran to C, what a mistake!), it's more important to know what it is doing (conceptually) than knowing how to convert.

What I mean is that I tried to convert ForTran to C. I would write C code that did exactly the same as what the ForTran code did. I did that for exactly one program. The rest of the conversions were done by figuring out what the input was, what the output was, and then rewriting (from scratch) everything in between. When I left that job, the only program that wasn't working was the first one. Everything else was working fine when I graduated from university (1997) and went back to thank my former manager for what I learned there.

The only exception was when I went back to look at the original code was when I couldn't figure out a mathematical formula - math is picky like that ;-)

Short version: what is a WSF file? What is your input, what is your output?

If ($argument->{CycleDate})  {
    $cycleDate = $argument->{CycleDate}
}
[download]