Odd global/public error, or User error?

The public array is still there in Module2. The Locals windows just shows variables local to the active Module, so is only showing the variables in Module3.

However, most uses of global variables should instead use parameter passing. What are you going to do with the array?

Originally Posted by 6StringJazzer

The public array is still there in Module2. The Locals windows just shows variables local to the active Module, so is only showing the variables in Module3.

However, most uses of global variables should instead use parameter passing. What are you going to do with the array?

Jeff, thanks for replying.

The array is holding a lot of in-process DNS string data essential in later sheets, manipulated in each sheet.
One sheet imports it into an array, another sheet will parse it for correctness, another will validate exported records to DNS name and IP, another sheet will identify related A/C records and ultimately create CLI commands which will delete records, and then re-create A records and related A/C records as dependents.
Each macro is called by User button press, and does not call any others.

I have it working fine if I create a separate sheet to import and export arrays to from each module.
However using Global arrays would reduce a lot of the import/export set-up, and simply flow easier.

I thought the whole purpose of having public, project-scope variables was to keep vars in memory, addressable by any module within the workbook.
I've read that using globals like that is frowned on by some, however this is going to remain a relatively simple workbook, with limited scope for addition, and I'm the sole owner.
My problem is, since other people are using the wb in a step-by-step fashion, they have to work on sheet 1, run macro 1, work on sheet 2, run macro 2, work on sheet 3, check previous work is correct, then run macro 3, etc.

So macro2 is creating the public scope array, however when that macro ends and Macro3 is called, it is not showing that public scope array.
So when MS say Global/Public, do they actually mean that or are they assuming it is global with that specific macro and addressable by multiple subs/functions encapsulated within that one macro?

Appreciate any insight.

Public is available to any routine in that project and any referencing project. Unless there is a state loss, the variable will still be available to macro 3. Have you actually determined that it isn't, or are you just going by what you can see in the Locals window (the word Local being key)?

rorya,

Good point, I'd just run across that in another post while posting above.

However, the last module2 statement is what fills the public array, and I don't see any state-loss before firing off Macro3

Please Login or Register  to view this content.

Locals window shows Locals, but also show Public right?
x5.PNG

Immediately after Macro2 runs, I step into Macro3:

Please Login or Register  to view this content.

It shows the Locals, however it does not show the Public-scope vars as it did in Macro2
x6.PNG

No errors are being reported or should that I can see, which would zero out the var's.

Open the WATCH window and add a watch for the variable so you can see its contents as the different procedures run.