|
Jim -
That's a new on on me for preferring non-numerical values for IDs. I was
always told it was better to use numeric keys. Then again most of the stuff
I have worked with is database driven and uses the primary key (autonumber,
no dups) as the ID or had employee ID's. I'll have to do some more looking
and reading about this idea. Any references you can pass along to this
concept?
Mike -
PERFECT! I ran the following sample code and things worked out exactly as I
was hoping for. I figured there had to be a way to do it I just didn't know
where to look. I'll have to add this to my very short list of tricks. Now
all I need to do is adjust the actual macro and that section will be
complete. Thanks!
/*Generate Blank Set*/
data Errors;
set _Null_;
attrib Name length=$80;
attrib Value length=$80;
run;
/*Brute force example of putting numeric/char into same char variable*/
proc sql;
insert into errors (Name, Value)
select Name, CATT(height) as value length=80
from sashelp.class
where height > 50;
insert into errors (Name, Value)
select name, CATT(sex) as value length=80
from sashelp.class
where sex="F";
quit;
| 
