Mystery - running in Dev Vs Exe file

[BlackWisdom]

I have only seen this in the latest version of Macro Scheduler:

I will design a script run it from the Dev environment - it works great, but when I compile it and run it - I get a series of errors on lines of logic that was not generating errors prior to compiling.

Or the reverse I will design a script run it in the Dev environment - it generates errors - but when I compile it - it works fine.

I have scanned for viruses and spyware - any idea..??? has anyone else seen this???

[CyberCitizen]

Any Chance Of Posting The Script So That We Can Have A Look?

[BlackWisdom]

Hi micheal ,

actually there has been numerous scripts - but here is one:


ReadLn>FolderTotal.txt,file
separate>file,%CRLF%,num
Let>k=1
repeat>k
Let>k=k+1
add>num_1,num_%k%
until>k,num_count

WLN>sum.txt,%num_1%


the error is caused by the add> statement (6th lind down)

[Bob Hansen]

Need to define num_%k% separately, something like this:

Code: Select all

Let>numadd=num_%k%
Add>num_1,numadd

[JRL]

Hi Bob, Michael and Black Wisdom

I agree that sometimes a variable needs to be defined twice when a sequential variable is involved.

I submitted this sample earlier today in response to a different question. It ran fine within Macro Scheduler. I tested it before posting. I will see what happens when I compile it tomorrow at work. I only have a non pro license to use at home.

Later.
Dick

[Bob Hansen]

I did not create a file of numbers, I just hard coded some numbers for test purposes. I found that if num_1 was not defined, that I got the error message. So I did Let>num_1=0 and message went away, Add worked OK.

I figured if I did a real Separate> command that it would work OK without having to define it.

Try doing a Single Step with Watch List on, and look at the values of num_?? before you get to the Add command. Perhaps Separate is the real problem?