It seems that what I want to do can't be done then.
Let me explain a little better what I am doing as you or someone else may have another solution.
In fact as I write this I think I have just solved it.
What I have is a whole bunch of different windows (and doors) in my library.
I need to output information from them such as height, width area, thermal transmitance of the unit, shading height and width, etc. for use in an energy efficiency calculation.
This all writes to an external text file so that I can cut and paste the information into a spredsheet (created by others) for the calculations.
Everything works fine.
But what I wanted was the room name that the door/window belongs to.
I thought zones would be ideal for this as I can also set up an automatic room name stamp for the plans as well get the room name for the door/window.
At the moment I have a value list of names the user can choose from manually.
Because I have many different doors and windows it made sense to run the script that writes the text file from a macro so I could just have the one script to alter if need be.
So I needed to parse the value of the zone name to the macro - but of course couldn't.
What I just realized though is that I can REQUEST the same zone information from within the macro itself and can then output this to the text file.
A simple solution really for what seemed to be impossible.
Maybe if I had explained this in the first place you would have suggested the same thing.
I'm still annoyed that you can't trap the value of the REQUEST variable for use in other areas.
Thanks again for being so helpful.
Barry.
One of the forum moderators.
Versions 6.5 to 27
i7-10700 @ 2.9Ghz, 32GB ram, GeForce RTX 2060 (6GB), Windows 10
Lenovo Thinkpad - i7-1270P 2.20 GHz, 32GB RAM, Nvidia T550, Windows 11