I have found different scripting environments sometimes have subtle differences in expected vb script syntax. This is not the fault of any scripting environment, it just reflects that different scripting engines are just slightly different from each other.
For example, I copied and pasted your supplied script into Microsoft Visual Studio 6.0, and it worked right off the bat with no changes.
I then saved the same script to an ASCII file locally, and called the script from Expedition using the Keyin Command toolbar. I ended up getting errors of different sorts until I changed the script to the following, which then worked as expected:
lTemp = "abc,def,jgj"
jArray = Split(lTemp, ",")
For i = 0 To UBound(jArray)
Sometimes you just need to play with the code a little bit to see what works for that scripting engine. Sometimes code from one environment requires a bit of tweaking in order to run correctly in another environment.
I hope this helps, good luck.
Has anyone found a resolution to this? I'm getting the same error. Do I need to update some Visual Basic Library or something? I'm using PADS 9.4.1 and I'm not really sure what to do.