In addition to Cynthia's suggestion, have a look at: ods tagsets.excelxp options ( SHEET_NAME = 'STATE' SHEET_INTERVAL = 'BYGROUP') ; If your data is sorted in state order and you do your report using a BY statement then the above will automatically create a new tab/worksheet for each state and will append a number on the end of the sheet name. This is a very easy technique to produce a multi-tab Excel workbook. ... View more

It would be helpful if you could supply the full code including your macro definition statements and macro call statement. The MPRINT evidence is suggesting that &commented may contain the text BY as well as the BY variable. If it is this should be removed. Supplying the full code would help clarify this. ... View more

I suggest you raise this with Technical Support as your message is the second in the past few months on this specific issue and the first one did not get resolved. ... View more

I suggest you check out the FREQ procedure. While it is more commonly used to do counts of each distinct value of a variable, it can also output a dataset that contains the distinct values of a variable, one per row. So if you count up the number of rows then you will have your answer. ... View more

If the only blank lines in your files are at the end before the descriptions then you could check for a blank line and then stop like this: data test; infile xxxx; input @1 check $1. @; if check ne '' then input ; else stop; run; The trailling @ sign will hold the current record for your full INPUT statement. ... View more

Have you considered using permanent SAS libraries to share SAS files between different Stored Processes? ... View more

The answer depends on the SAS server your EG is connecting to. It is possible for EG to use SAS on your desktop, but only if a complete SAS install has been done and not just EG. In this scenario a %include will look on your desktop hard drive. More typically EG connects to remote SAS servers so it will be the hard drives of those servers where a %include will look. Check your EG connection to confirm where SAS is running. ... View more

One point not touched on in this very interesting thread is that if EG is the ONLY SAS interface on your desktop then you completely lose the ability to do local SAS processing. There are many valid reasons for maintaining a full desktop SAS installation even if most processing is server-based. These include running local jobs when your server is heavily loaded, directly exporting/importing Microsoft files using SAS code to the desktop, and being a cheap Disaster Recovery option when your server has no DR plan. We run a lot of business-critical processes so we need this as a backup plan. The side benefit of full desktop SAS is you maintain the flexibility of being able to use EG or DMS both for local and remote processing. The choice remains yours! ... View more

I suggest you explore FTP (File Transfer Protocol) as a way of moving your files from Unix to Windows. FTP is built into both operating systems and you can get SAS to do the FTP for you using a FILENAME statement with the FTP option. The first thing you will need to check out is can you logon to your Windows network from your Unix server. Since you haven't worked with Unix before I suggest you get help from other Unix users at your site to confirm you can do this. From a Unix command line you can test a Windows connection by typing ftp then type open . It will then prompt you for a userid and password. ... View more

I don't use EG much so I won't comment on editor differences between EG and DMS. What I would like to say is that where I work, we continue to use full SAS on our desktops even though we primarily use a Windows SAS server. Why is this? One of the important reasons is that there is NO DR (Disaster Recovery) plan for our SAS server. If for any reason it is not available we retain the capability of running our business-critical processes from our desktops (after our data is restored on a file server) so at least we have some minimal DR/backup capability. All our programs are written with this flexibility in mind. I wonder how many SAS sites are in the same boat? If your SAS server has no DR or backup and you only use EG - tough, you have no alternative! BTW I use DMS line numbers all the time as a very useful productivity aid. ... View more

I suggest you use the computed column option, and the Advanced Expression Editor to type in the INPUT function as I have already mentioned, to create a new computed column that converts the character column to numeric. Then you should be able to use the new computed column in your join. ... View more

If you have a very large dataset and do not want to sort it there are at least two good choices: 1) Hash join table B to table A in a DATA step, as mentioned by Peter. 2) Create a SAS format from the username in table B using PROC FORMAT, then use the PUT function in a DATA step to do the lookup. Both of these techniques provide similar (very quick) performance as the lookups are done in memory. They are well-documented in online help so I would suggest doing some research yourself if you would like to check this out further. ... View more

I agree it would be easier to write to the SAS server location directly from the PC. If the server were running Windows this would be dead easy as the file location would become: \\servername\apps\jobs\test.sas It looks like the server is running Unix judging by the directory name so unless the server has NFS (Network File System) enabled, I suspect for someone new to SAS a single remote submit uploading the data and writing it is going to be the simplest approach. Message was edited by: SASKiwi ... View more