http://blogs.sas.com/content/sasdummy/2014/08/29/experimenting-with-ods-excel-to-create-spreadsheets-from-sas/ ... View more

Or using DOW: data have; infile cards; input (Name                    city                         county) (:$); cards; Ann                        A                             1                             Betty                      B                             2                             Carol                      A                             1                             Dave                      B                             2                             Ethel                      A                             2     ; proc sort data=have; by county city; run; data want; length group $40; do until (last.city); set have; by county city; group=catx(',',group,name); end; run; proc print;run; Haikuo ... View more

And, usually, it is only the SASUSER library that becomes read-only on the second and subsequent instances. So if you are trying to write to SASUSER in the second instance, you might have an issue. You only can have 1 write-access copy of SASUSER open at a time. All subsequent instances of SAS open a read-only copy of SASUSER. This mostly impacts SASUSER.PROFILE and SASUSER.REGSTRY. The files are usually copied to WORK for the session, and if something can't be copied, you see messages about that, too. Typical messages you get in the log are: NOTE: Unable to open SASUSER.REGSTRY. WORK.REGSTRY will be opened       instead. NOTE: All registry changes will be lost at the end of the session. WARNING: Unable to copy SASUSER registry to WORK registry. Because of          this, WARNING: you will not see registry customizations during this session. NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened       instead. NOTE: All profile changes will be lost at the end of the session. NOTE: This SAS session is using a registry in WORK.  All changes will NOTE: be lost at the end of this session. NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened       instead.   Here are some Tech Support notes about the issue which might be relevant to your configuration: http://support.sas.com/kb/13/838.html http://support.sas.com/kb/12/502.html http://support.sas.com/kb/13/803.html http://support.sas.com/kb/8/538.html cynthia ... View more

I got it.  DATEPART did the trick. ... View more

If you are populating the Excel table from within SAS the EXCELXP tagset has the capability to take advantage of excel functions.  questions on this tagset are best posted in the ODS forum. ... View more

did you create an autoexec program in 9.2 to define the formats? ... View more