As per my personal view i think the usage of SAS might drop down alot but it wont be expired . It is still one of the most important analytic platform .  ... View more

Thanks Reeza.You are the best!!   I will let you know how it goes ... View more

I am running this off of base sas desktop install ... View more

And it may just be that the format is too small to display well. data _null_; x=12345678; put x= best4.; run; Displays x as 12E6 because I told it display with only 4 columns. So the closest value SAS can display with 4 columns is the exponential.   ... View more

If your on a Windows-based system you can do it with the macro you can find at: http://www.sascommunity.org/wiki/A_Poor/Rich_SAS_Users_Proc_Export   Art, CEO, AnalystFinder.com   ... View more

@cynthia I created a blank row in the table and spit it out and it worked I appreciate your patience and support ... View more

@JasonNC The SAS Add-In for Microsoft Office (SAS AMO) uses VBA as well and will allow you to already do quite a bit without VBA skills. Having such skills will help you though to further extend functionality if and as required.   Keep in mind though that using VBA and Excel formulas means that you'll never be able to run your processes fully "enterprise grade" automated server side in batch (you can automate on client side but it requires your machine to be up and running).   As for DDE: Don't use it! All the explanations here: “Why your DDE programs don't work anymore”; http://blogs.sas.com/content/sasdummy/2014/10/14/dde-is-doa/           ... View more

options missing = ' '; ... View more

As far as I know you've got basically two options if you want to influence how and where heterogenous joins are executed. 1. You load your smaller table into the DB with the larger table. You can use a temporary table for this  https://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0irpkyp22l7vzn1il9lx6f4wmx9.htm 2. You pack the key values of the smaller tables into a where clause for a SQL sent to the DB with the larger table. That's what you're currently doing.   In a company I've worked many years ago we've actually implemented a "sqlpump" macro which did exactly what you're doing now: Pack the keys into a macro variable and then send the SQL to the DB for execution; and we've implemented in a way that this executed in multiple iterations when there were too many key values and then appended the result back in SAS. BTW: I believe some DBMS have a restriction of 32KB for SQL's so you want to limit your macro variable to something a bit lower than 32KB per call.   I believe that there is now a SAS dataset option DBMASTER which triggers SAS/Access to generate such code when using implicit SQL. https://support.sas.com/documentation/cdl/en/acreldb/69580/HTML/default/viewer.htm#n0jg0sozl17mjyn1woelrrr76266.htm    When using implicit SQL (so not pass-through) then also use the following options:  options sastrace=',,,d' sastraceloc=saslog nostsuffix;   This will show you in the log what SQL the SAS/Access engine actually sends to the database for execution.   ... View more

Jason,   In addition to Kurt's comments, you may need to talk to your IT support to get permission to use the local smtp server. ... View more

Hi Art,   It's weird I closed the session and ran the code again it worked ... View more

When all else fails, ask WWACD? (What would Art Carpenter do?> ... View more

Hi: ODS TAGSETS.EXCELXP is actually creating an XML file -- Spreadsheet Markup Language XML from the Office 2003 standard. When you name the file as .XLS, you are just "fooling" the Windows Registry into launching Excel to open the XML instead of launching a browser or some other XML application. When you use ODS EXCEL, you are moving into the Office 2007 world, where Excel, Word and PPT all got new file extensions: XLSX, DOCX and PPTX. These NEW extensions are NOT the same as the 2003 XML and they are not binary XLS files. So it would be wrong and inappropriate to name an ODS EXCEL file with the .XLS extension. It MUST be given a .XLSX file extension. If you use .XLS, then Excel is not happy. However, if you try this: ods excel file='c:\temp\class.xlsx' style=htmlblue;    proc print data=sashelp.class;    run; ods excel close; Then it SHOULD work. If this works and your code does NOT work, using ODS EXCEL and the .XLSX extension, then you have an issue for Tech Support. cynthia ... View more

I've never used rsubmit to run the macro, thus can't be sure of the reason. One possibility, though, is that you'll need to include the server_path parameter. It's described in the paper that's on the same page as the macro.   Art, CEO, AnalystFinder.com   ... View more