Try this - and also do the suggested reading: data Uniquepolicy; set Sortedpolicy; By POLICY_SK; rename TRAN_SEQ_NUM=MAX_TRAN_SEQ_NUM; /* output last row per distinct POLICY_SK */ if last.POLICY_SK then output; run; Message was edited by: Patrick ... View more

I assume, unlike the others, that SAS isn't on the mainframe. In that case you have a few options: Read directly using ftp access method and appropriate formats (s370 series) If data is text, and doesn't contain binary / packed or other mainframe formaatted fields, ftp to the unix box and let ftp do the conversion from ebcdic to ascii. There are other ways, but these are simple and straightforward. ... View more

It did work.Thank you. About the Class, that is in my original table. I was simplifying the table for this forum. Thank you very much. ... View more

If you do a PROC CONTENTS between the IMPORT and the SQL, you will see the fields that are of mis-matched types. It is fairly common for IMPORT to guess the wrong data type on .csv files. The GUESSINGROWS statement can help it get it right. Another possibility would be to use EGuide 4.2 to set up the data read. The code that it generates is much more robust than the basic SAS 9.2 IMPORT. You can then copy that code into your program. Doc Muhlbaier Duke ... View more

there is a SAS product that might help. See http://support.sas.com/kb/20/325.html 20325 - Using the EXPORT procedure with DBMS=XLS in 9.1.3 SAS/ACCESS® Interface to PC Files under UNIX to create a Microsoft Excel ... View more