Command Line Arguments

[jbg1978]

I have a script that runs perfectly when started from the editor, but when ran as an executable return a subscript out of range error. The only difference I can think of, is that when I run it from the editor, I give the strings explicit values. However, when I run the .exe, I pass the strings in through the command line. I can only assume that there is a maximum amount of subscripts that the $CmdLine[] variable can hold. Can anyone confirm that? I am trying to pass 8 parameters into it. Can I change the maximum?

Thanks,

Jason

[PsaltyDS]

I have a script that runs perfectly when started from the editor, but when ran as an executable return a subscript out of range error. The only difference I can think of, is that when I run it from the editor, I give the strings explicit values. However, when I run the .exe, I pass the strings in through the command line. I can only assume that there is a maximum amount of subscripts that the $CmdLine[] variable can hold. Can anyone confirm that? I am trying to pass 8 parameters into it. Can I change the maximum?

Thanks,

Jason

There is no such limit, however the Windows shell limits a single command line to either 1024 or 4096 characters, depending on version. More likely you are passing long strings as parameters that are getting clipped.

Another possibility is bad pairing of quotation marks on the command line.

Debug by just putting _ArrayDisplay($CmdLine) at the top of the script to see the inputs.

Edited September 11, 2009 by PsaltyDS

[hydroxide]

There is no such limit, however the Windows shell limits a single command line to either 1024 or 4096 characters, depending on version. More likely you are passing long strings as parameters that are getting clipped.

Another possibility is bad pairing of quotation marks on the command line.

Debug by just putting _ArrayDisplay($CmdLine) at the top of the script to see the inputs.

Agree here.. quotation marks for values which include white spaces.. we don't know your data, but does it have strings with white spaces?.. they all get treated as diff params from command line

Also watch out for special chars / chars reserved by CMD.. like ampersand

Edited September 13, 2009 by hydroxide