Here a short explanation what can be done and what cannot be done.
First some rules:
- WinBuilder Script Line Parameters are separated by a comma.
If a comma is inside an argument, it must be 'escaped' by #$c
- Besides some special cases (e.g. parameters in ShellExecute) generally enclosing quotes are not needed.
- Enclosing quotes MUST be used if the WinBuilder Script Line Parameters contain spaces
If the spaces are replaced by the escape #$s, the enclosing quotes should be ommitted.
E.g. unnecessary enclosing quotes or a comma inside an item enclosed by quotes.
But sometimes that can bring unexpected results.
Let me give an Example:
Item1,item2 is understood as two items, separated by the comma.
Item1#$citem2 is correctly written to have one item with the comma inside.
"Item1,item2" is wrong written, but by WinBuilder also understood as one item.
Now the problem-version:
Set,%Var%,"Item1","item2" cannot be understood uniquelly by WinBuilder.
Let's exchange the English understandable words by the chracter 'x'
Are there two quote-enclosed xxxxx, separated by a comma? > Set,%Var%,xxxxx
Or is there on long string of 10 xes, interrupted by a nested quote pair containing a comma? > Set,%var%,xxxxx#$q#$c#$qxxxxx
Or is there on long string of 10 xes, interrupted by a nested quote pair 'escaping' a comma? > Set,%var%,xxxxx#$cxxxxx
You see how important it is to follow the rules, even if WinBuilder understands most violations correctly.