compiler error

[JesseGrune]

Hello,

Have any of you had an unusual error in which hundreds of lines of similar code are fine and then one line generates an error that an end statement is needed? I checked all my code and every loop had both a start and a stop.

I was trying to replace people by having an automation pull data from excel, sort the data into arrays based on location, and then add sets of locations to location clusters so that Client Access could process the information.

When the basic idea was tried in a .VBS file, it worked.


dim array1(1), array2(2)

array2(0) = value1
array2(1) = value2
array1(0) = array2


In the above example, array1(0)(0) = value1 and array1(0)(1) = value2.

I do not know why the compiler that runs *.vbs files can execute that code and the one for Client Access can see nothing wrong with that code until it is used over 100 times.

Is Visual Basic any better than VBScript for consistently compiling code; or, is it just a bug that IBM has to fix?

Jesse Grune.

It was easy to read from Excel. It was easy to sort the data. However, the compiler crashed when I tried assigning arrays to indexes of another array.

 

[JesseGrune]

Never mind. I found out that, due to some security feature, scripts that import data from an external source are scanned before being compiled to stop them from running.

As a result, I cannot import data from Excel until my security clearance is raised.

I did not know security systems became so good.

Jesse Grune.