I am attempting to get a table created by a stored process to render with frozen column headers.   I have referred to a number of support documents that explain ODS TAGSETS.TABLEEDITOR and only get partial success with the options.   For example, autofilter="yes" does work in both IE 11 and Firefox 30, but frozen_headers ="yes" and  frozen_rowheaders="1,2" don't seem to work, either separately or together.    I have tried setting table height and width to ensure the table would not fill up the screen (what a mess looking at Google Chrome).  I am creating the stored process using Enterprise Guide 4.3.   When I look at the examples presented in the document Creating a Data Grid Like VB.NET, the frozen_headers.htm example also does not work.   I was thinking I might have a local environment issue, but some of these options do work, so I'm stuck as to why the frozen headers won't work.   Any ideas?    Thanks. ... View more

Is there a way to make a stored process prompt dependent on the value of _METAUSER? ... View more

In SAS, I can attach a macro variable to a column name.  For example: %let year=2013; proc sql; create table student as select id, major as MAJOR_&YEAR ... This results in a column name of MAJOR_2013. I'm trying to do the same thing in DI Studio.   When I map from the source table to the target, I rename the target table column MAJOR_&YEAR.    The result is then MAJOR_&YEAR rather than MAJOR_2013 like I get in SAS.   Even if I put that macro variable in quotes, like MAJOR_"&YEAR", my resulting target table column name is MAJOR_"&YEAR".   I am either doing something wrong in DI Studio or DI Studio doesn't behave the same as SAS in this particular situation.   Has anyone successfully used a macro variable in a column name in DI Studio?   Thanks. ... View more

I am faced with two challenges in creating ODS output with SAS 9.3.   I am creating a mail merge data file with an ID column, then 6 additional columns with messages.   Everyone will have at least one message and some will have more than one up to the six, meaning lots of empty cells all around.   Some messages contain over 1024 characters.  The ID cell can have up to two leading zeroes.  I have tried to create a modified csv tagset to deal with leading zeroes and that seems to work in a very simple query, but when I assign the adjusted templace to the ODC CSV process, the output is garbage.   Quotes start appearing in multiple columns and many columns are shifted. If I use the plain ods csv process and add an options (quoted_columns='1'), then my column layout looks great, but I don't see leading zeroes appearing on IDs in that first column.   Trying to add this quoted_columns option to the modified tagset causes a crash.  I might not be adding it correctly, though. I can't use ODS EXCELXP because of the 1024 character limitation. Any ideas are appreciated.   Thanks! ... View more