So if you want varying number of variables , I recommend to use Patrick's code PROC TRANSPOSE. Ksharp ... View more

Arthur, I think using MEMBERS table is pretty faster than TABLES table. proc sql;   select memname     from dictionary.members       where libname="SASHELP"   ; quit; Ksharp ... View more

Thank you Art, also I found an option works well ,but just for mininize ,can't run at background or invisible: options noxwait noxsync xmin; ... View more

Thank you Art,this works ! ... View more

Thank you,I download the macrofun file and found the help for my question: ERROR(enable_logical, macro_ref) Enable_logical    is a logical value or number that selects or clears error-checking. If enable_logical is FALSE or 0, all error-checking is cleared. If error-checking is cleared and an error is encountered while a macro is running, Microsoft Excel ignores it and continues. Error-checking is selected again by an ERROR(TRUE) statement, or when the macro stops running. WORKBOOK.INSERT(type_num) WORKBOOK.INSERT?(type_num) Type_num    specifies the type of sheet to insert. Type_num Type of sheet 1 Worksheet 2 Chart 3 Excel 4 Macro Sheet 4 Excel 4 International Macro Sheet 5 (Reserved) 6 Microsoft Excel Visual Basic Module 7 Dialog quoted text Template If omitted, the type of the active sheet is used. If the current selection contains one sheet, then only one sheet is inserted. If the selection contains more than one sheet and the active sheet is a worksheet, then an equal number of sheets is inserted to the left of the selected group of sheets. Also ,I get another question: Could we use our user defined excel macro in the put [] command? that would be very interesting. I will try this later. Thanks Mike ... View more

Thank you Art! I tried "save as" didn't work,but as your advice use "save.as" will works ! ... View more

The issue is that SAS does not have a PASSWORD= option, so you need to use one of the work around methods mentioned in the thread linked by haikuo bian above.  Read the thread and the papers that are linked in that thread. If you still have detailed questions then ask them. ... View more

Art, It doesn't get any better than that.  Good solution. ... View more

If by batch you mean submitted to the background from a terminal (or on a personal computer) then it pops up the window and waits for you to hit enter. If you submit it without a terminal attached (-noterminal command line option) then SAS generates an error message: ERROR: The MACRO windowing environment cannot be initialized due to a XU supervisor failure. I would assume the same would happen if you submitted from EG as would expect that the SAS server process is running without a terminal. ... View more

Google "findstr", here is one hit:  Findstr - Search for strings You could also use Powershell but that would be slightly more complicated.  I do like Powershell's support of context, where you can print x number of lines before or after the text match. Google "powershell select-string", here is one hit:  Select-String and Grep - Windows PowerShell Blog - Site Home - MSDN Blogs HTH, Scott ... View more

Not sure what the advantage would be.  But to be able to do it exactly that way SAS would need to be a compiled language instead of an interpreted one.  You could structure your source that way in SCL since it needs to be compiled. If you really wanted to create code in that form you could wrap the main routine in a macro and then call it at the bottom of the file after all the sub macros have been defined.  But I do not recommend it. %macro main;   %sub1;   %sub2;   ... %mend main; %macro sub1; ... %mend sub1; %macro sub2; ... %mend sub2; %main; A more natural process would be to create autocall library for the subroutine macros. Create a separate file with each macro's definition and store them in a directory.  Then you main program could look like: options sasautos=('mymacros'); %sub1; %sub2; ... View more

data one; a="123#45#678#9"; b=count(a,'#'); run; ... View more

data one; a="asd1,2,ggg3,678,thy%@#@;"; b=compress(a,',','dk'); run; proc print;run; ... View more

There are many limitations to update operations with Excel. Here is what works, at least with Excel 2003 and Excel 2007 : libname xl Excel "&SASForum.\Datasets\Append.xls"; /* Create the Append.xls workbook with a sheet named myData$ and a named range called myData */ data xl.myData;      x = 1;      run;   %macro append; %do i = 2 %to 5;      data have&i;           x = &i;           run;      proc sql;   /* Save the contents of the Excel table */           create table have as                select * from xl.myData;   /* Erase the contents of the table in the workbook, Excel doesn't allow you        to overwrite an existing table */           drop table xl.myData;   /* Recreate the table with your added lines. It will replace the old version        at the same place, with the same cell formatting */           create table xl.myData as                select * from have                union all                select * from have&i;           quit;      %end; %mend append;   %append; libname xl clear;   PG ... View more