To necro a post is to raise it from the dead.  This thread is from 2015, it is very old.  Posting again to an old thread raises it back up to the forefront, I for instance know this because I get automatic emails from posts I have contributed to, so as you can imagine, if people starting posting in all old posts, my email would collapse.  You can show your apreciation to posts by clicking the Like button below the post. Also note that old posts my not use current thinking/technology.  For instance if you are using an XLSX file, and have SAS 9.4 then you can far simpler access data by using the libname excel engine: http://blogs.sas.com/content/sasdummy/2015/05/20/using-libname-xlsx-to-read-and-write-excel-files/ ... View more

Hi @AnnaShami,   Try unchecking the "Open output data automatically" option in the SAS Addin for Microsoft Office's Tools->Options->Data->Output Data Sets.  That should prevent output data sets from being automatically opened in Excel.   Casey ... View more

I got response from SAS Technical help, it works like magic for this partuclar project. Here is the solution:   Tools > Options > Results > Results General, then you will see the option 'Prompt before opening results larger than:" then specify some value. In addition, on the same page, you might want to  un-select the option "Automatically open data or results when generated". ... View more

I am afraid that there really is no easy programmable way to tell. I would reach out to the data provider get some metadata information, at least on ballpark level, such as how many records, fields in total etc, and understanding how the data is generated also helps, for instance, if you know you are get whole year of data that is collected on monthly basis, then there is a chance of your having 'end of file' symbol embedded. ... View more

I think that is onto something. I would suggest that you test his hypothesis with some very simple code that would pull some data out of one of your tables using the pass-through syntax that you are trying to use. Without knowing anything about your database, I would use something like this to prevent putting any load on your environment: %LET facid=("DSN=Reporting;" || "UID=rp&UID.;" || "PWD=&pwd.;" || "SERVER=cbcfrpt00"); proc sql; connect to odbc &facid; create table work.TestOutput as select UMUM_REF_ID from CMC_UMUM_UTIL_MGT(obs=10); quit; If you get data back, it means that your macro variable is working correctly. If not, you'd need to tinker with your macro variable and connect statement until you get data back. Then you can proceed with your more complex statement. Tom ... View more

Sometimes this is a result of a change from 32-bit SAS for Windows to 64-bit: The top gotchas when moving to 64-bit SAS for Windows - The SAS Dummy Chris ... View more

Thanks Barnipaz and Tom. We have EG SAS on the server. Does that mean the codes I had initially won't work on the server? Second, I tried Printto it worked 🙂 Thanks ... View more