About the concat: I will follow your hint of not using percent-signs at the position of the destination variable, thanks. Excellent example of yours by the way about assigning a value to "nul"! Single character names: you are totally right, in my daily work I never use these! But in my example I use...

Great you have found that too! It matched perfectly with my first example. And sorry for not finding your article from 3 years ago. But besides the different number of resolving steps for the first and second parameter of the concat, another problem seems to be there in the code below: (I tried to m...

Hi, I am not very familiar yet with the method(s) used in Macro Scheduler to resolve variables. I have already seen very interesting topics about usage of %-signs, one of them is that you better not use them unless they are really necessary. But before I was aware of that, I did the experiments belo...

Ok, thanks for telling to not use concat. So then I won't be hurt by next too: Perhaps the use of the %-sign for the destination parameter of a concat-statement in the code below is not allowed/or not adviced, but a strange new variable is created after execution. Note that Macro Scheduler seems to ...

Hi, Below I added 2 pieces of code. The first one works very well, however, I try to minimize using VAREXPLICIT. The second one, using the default VAREXPLICIT=0, comes up with something I did not expect. [color=green]//Snippet 1: //Re-start here using <F8> Let>VAREXPLICIT=1 let>a=b let>b=c let>x=%a%...