There is no "transfer from Excel to SAS" -- you are faced with doing your input-handling from SAS to connect to the SharePoint server/machine "source" location to read/process the data and generate a suitable SAS-representation, likely with a FILENAME / DATA step processing. Obviously you will need to gain access-authorization to the SharePoint-deployed system/server, working with your SharePoint admin staff, while also making available the specific location where the "source" SharePoint data file/folder(directory) is located.  Recommend to start with confirming that FTP direct-access (outside of SAS) works as expected, then progress to compose your SAS-based input-processing SAS script(s) as needed to process the data. Make good use of the available SharePoint related resources / papers / posts on the SAS support website. Scott Barry SBBWorks, Inc. ... View more

Not likely that you associated any "SAS" specific reference to the SharePoint data.  Most likely is that you are faced with exporting "survey" type SharePoint data as an Excel-type data-format, possibly even resorting to column/row CSV-type input handling which SAS can deal with easily -- also, most likely needing to use SAS input-handling process via an FTP-like connection. To consider prior SAS-related discussion, recommend an Internet search, such as argument-string as:   sharepoint data site:sas.com Scott Barry SBBWorks, Inc. ... View more

Clarify what exactly is meant by"...assign variable labels in SharePoint..." - as in what type of "published document" is of interest to interpret and how do you intend to access/retrieve the data objects from SAS? Scott Barry SBBWorks,Inc. ... View more

Can be accomplished programmatically, using the DATA step function VNAME to assign a numeric value for WEEK - based on a SUBSTR(...) and output each variable instance from inside a DO/END loop using an array that references the w#_xxxxx and m#_xxxx variables. Another possibility is to use DICTIONARY.COLUMNS to generate the required SAS code based on the actual variable names found -- again, without any hardcoded programming where the "#" must already be known. Scott Barry SBBWorks, Inc. ... View more

As well as not being hard-sold on using the SAS MACRO LANGUAGE, also consider the opportunity to use the INTNX function to establish/reference your intended max-cutoff dates as you code your IF/THEN/ELSE... file-split DATA step logic. Scott Barry SBBWorks, Inc. ... View more

Suggest you run again with OPTIONS parameters that will increase the useful SAS log program compilation diagnostics, OPTIONS SOURCE SOURCE2 MACROGEN SYMBOLGEN MLOGIC;  -- some of which would not necessarily apply here, without MACRO usage. Also, as was suggested, strip-out all but the bare-essential SAS processing to generate the EMAIL -- that would be the "resuting code" generated from the CALL EXECUTE -- no surrounding DATA step.  And then work your way backwards, one step at a time. And, your use of FILENAME is not part of the CALL EXECUTE, in case that's what you intended. Reviewing CALL EXECUTE, that SAS code will be compiled and executed only after the current DATA step completes. Strongly suggest you start simple then increase complexity, only after suitable self-initiated desk-checking. ... View more

Recommend you extract from your overall SAS code (shared in the post) an explicit SAS program script that demonstrates what you wish to accomplish -- then slowly amend the SAS execution code to piece-by-piece add in each automation-aspect you are wanting to have work. From what you contributed, there are multiple instances of missing semi-colon characters (code line termination) which will influence the success/failure. Desk-checking your SAS program is going to be a good start....only then after you get some SAS log results, you should consider sharing this additional information -- rather than just the SAS code you would like to think will work. Essentially, start with the simplest of intentions with what you are trying to achieve and then sculpt the masterpiece iteratively.... ... View more

SCAN works well, either supplying a positive-value argument (from start-location) or negative-value (from end-location) -- will depend on the result/requirement, however there are likely multiple SAS functions that can accomplish the task.  Similarly, various SAS concatenation functions as well will apply, such as CATX, or using TRIM, possibly even COMPRESS, depending on the rqmt. Scott Barry SBBWorks, Inc. ... View more

Interesting - for both SAS Windows and SAS z/OS (IBM mainframe), I use a remote "SMTP mail server" although my ATTACH=(....) file is local to the system where SAS is executing.  Does that jive with your experience, Cynthia? Scott Barry SBBWorks, Inc. ... View more

Also, as to your question about capturing/reporting processing-time:  the SAS DATA step function DATETIME() can capture the current date/time into either a SAS DATA step variable or also using SYMPUT you can capture the character-string equivalent to a SAS macro variable.  With this coding technique applied, then any SAS code-piece can have a pre-processing (initialization) DATETIME() data capture and a post-processing (clean-up) execution to derive an elapsed time. And with this information, your options are to either make use of MACRO variable "passing" between the initialization and clean-up code-points to derive an elapsed-time data value -- or otherwise more simplified approach having a SAS temporary dataset with the variable containing the start-time and then having the end-time to compute a duration-execution. ... View more