Clearing object variables from RAM upon conclusion of procedure - VBA

Question

I recall being taught that good programming clears object variables from RAM by setting them to nothing at the conclusion of a procedure.

Is my recollection correct?

Is this still a good programming procedure with VBA?

Answer 1

Yes, it's a good practice to follow. It often doesn't make any difference, especially if the objects are small, but always doing it forms a good habit.

VBA *should* clear all local variables (those whose Dim statements appear inside a procedure) from memory as the procedure ends, but I'm not sure that always happens for object variables. The difference is that scalar (non-object) variables are stored at addresses within the procedure's stack, but object variables are stored on the "heap" and then referenced by a pointer. Clearing the stack is easy, but cleaning up the heap is harder.

Answer 2

Thank you Jay. I will continue to do it, it can't hurt.

Answer 3

Although others are welcome to chime in, I think I found the answer.

In general subroutines, unless the object is holding a LOT of information, don't bother. It will be emptied when it loses scope.