Afaik proc export does not support the use of stylesheets at all. ... View more

Stop tearing your hair out, the internal code of proc import has never been printed to the log. ... View more

Hi DWW, try using the IN-option when merging the dataset. Both datasets have to be sorted by Cust, Prod and Cost. Example [pre] data work.c; merge work.a work.b(in= inB) ; by Cust Prod Cost; if inB then delete; run; [/pre] ... View more

Please don't double post questions in multiple forum. >> http://support.sas.com/forums/thread.jspa?threadID=5029&tstart=0 ... View more

If SAS/STAT is installed, have a look at the surveyselect procedure documented in http://support.sas.com/onlinedoc/913/getDoc/de/statug.hlp/surveyselect_index.htm#idxsus0002 ... View more

You can use the XML libname engine to access xml-files. The engine is documented in http://support.sas.com/rnd/base/xmlengine/sxle913/index.html ... View more

It is hardly possible to find the solution without knowing what error message you got. ... View more

You can use the %scan-function to extract the part before .txt, afterwards it may be necessary to remove any other char not allowed in dataset names. The translate function could be useful for that job. ... View more

Using a DATA STEP with the MERGE statement and the in= Option for Data2 is the common way to get the result. Both datasets must be sorted by "Id" and "Month". ... View more

Is this a sas problem? Have a look at the dopen function: http://support.sas.com/onlinedoc/913/getDoc/de/lrdict.hlp/a000209538.htm ... View more

Afaik it is not possible to hide the work-datasets, you could delete them by using proc datasets if they are not useful for anybody. ... View more

As far as I know, dynamic parameters are not supported in EG 4.1, but will be included in 4.2. ... View more

... telling me the number of times the ID is repeated or not ... It seems that you don't know how sas process data, although it is possible to read more than one observation per iteration, I doubt that your problem is solved that way. Maybe you should have a look at the documentation provided by SAS on http://support.sas.com/documentation/onlinedoc/base/index3.html, especially the "SAS 9.1.3 Language Reference: Concepts" could be of iterest. ... View more

It is not necessary to open a second thread for the same topic. http://support.sas.com/forums/thread.jspa?threadID=3901&tstart=15 Does the number in "employee1" depend on a) the number of the current obersavtion, b) any other variable in that oberservation? One possible solution: [pre] data work.extended; set i; length employ $ 15; /* defines a character-variable, with enough space for 15 chars */ employ = cat('employee', _n_); /* _n_ = the number of the current obersvation */ run; [/pre] ... View more

The problem is that you are mixing macro-code and normal sas-code. In this case the intnx-function will never be executed. Some functions can be used in macro-statements via the %sysfunc-macro-function. The following code uses a data-step to create the macro-variable firstDay. [pre] data _null_; firstDay = put(intnx("DAY", "31Mar08"d, 1), mmddyy8.); call symput("firstDay", firstDay); run; TITLE; TITLE1 "Date = &firstDay"; proc print data=sashelp.class; run; [/pre] Thinking before the first coffee is not always a good idea 😉 I removed the wrong idea about intnx and sysfunc. Message was edited by: andreas_lds ... View more