Variable Scope

[JimS]

I have an event procedure for a form control that steps through selected rows
of a list box and does some actions. One of the columns is multi-valued (1 or
more values separated by semicolons). I use the split() function to put the
column into an array and rifle through its values.

My issue is the array's scope. I declare it inside an if statement deeply
within a larger loop that steps through the rows.

Will the variable go out of scope (I want it to...) when it steps to the
next row in the outer "for each" loop?

If not, how do I reinitialize it so its lower and upper bounds are reset?
Does the assignment to the value of the split() function do that
intrinsically?

 

[Rick Brandt]

I have an event procedure for a form control that steps through
selected rows of a list box and does some actions. One of the columns
is multi-valued (1 or more values separated by semicolons). I use the
split() function to put the column into an array and rifle through
its values.

My issue is the array's scope. I declare it inside an if statement
deeply within a larger loop that steps through the rows.

Will the variable go out of scope (I want it to...) when it steps to
the next row in the outer "for each" loop?

If not, how do I reinitialize it so its lower and upper bounds are
reset? Does the assignment to the value of the split() function do
that intrinsically?

A variable declared anywhere in a VBA procedure always has procedure level
scope regardless of where in the procedure it is declared. In fact, a
variable declared inside an If-block is still instantiated even if the the
"if" test is false.

Each usage of Split() should reset the size of the array automatically.

 

[JimS]

Perfect, Rick. Thanks for that very lucid response!