Another encounter with the OutputTo command

[Micron]

I asked in post 2 if both forms were open. That code suggests neither was open.
I wouldn't expect it to output even once for a form that wasn't open.

[GraeagleBill]

I wouldn't expect it to output even once for a form that wasn't open.

Ah, me dummy in assuming that OutputTo implies that form opens first in the process of "outputting". Notice in final code that each iteration shows "Open", "OutputToo" and "Close". Each instance of "Open" in loop configures form for the designated floor as taken from the global variable "strCurFloor". I tested that if "Open" and "Close" sequence done outside of loop that I get 4 copies each of the same 1st floor, which I expected given newly found wisdom from Micron

[GraeagleBill]

Does post #17 answer post #15 question?

[Welshgasman]

Does post #17 answer post #15 question?

Yes also it does answer post #9?
I would tend to prefix globals with a 'g' to identify them? Then it negates questions on unused variables as it is clear they were defined globally outside the scope of the code posted.

[Micron]

Then it negates questions on unused variables

I'd rather that all OP's divulged that information. Don't know if I'd clue in or not since that's not my style. Those who have no clue about scope (lots of code is just copied) won't say because they don't know better. Those who do know should say but for some reason, don't. That just wastes time asking about the not so obvious.

[GraeagleBill]

prefix globals with a 'g' to identify them

Great idea. I've always appreciated the conventions of prefixing objects and data types so identifying global variables as such will be a great help.

[GraeagleBill]

Some really good points added to the OP regarding clear variable identification. Since I'm a big user of global variables, perhaps some of my past posts were lacking where I failed to clarify? As posted in #21, I'm adopting Welshgasman's suggestion.