@ADoering wrote:
Thanks everyone.
I take it there is no optimal solution (like vvalue() outside data step, or put() with a default), but I like the ideas of
having views with both formatted and raw values for our main tables
creating a fmt% macro as presented by mkeintz, but combining with unison's suggestion to derive it automatically - since formats are unique to the variable name in that environment accross tables, this shouldn't be an issue - I'll see if I can even combine it with use of vvalue where applicable if not a variable in one of our standard tables. I'd post it when I get to do it - or accept it as a solution, when someone else does 🙂
I appreciate the idea of dynamically generating the format, using metadata in the data set header information (or maybe PROC SQL dictionary
and I wonder whether a DOSUBL macro calling function would be the technique to use. Unlike other uses of macros the it does not need to be resolved prior to execution of the call data step. But I have never needed to find out more about DOSUBL. If someone on this thread could prove or disprove my conjecture, I would be very interested.
... View more