Did you miss the Ask the Expert session on Introduction to SAS Add-In for Microsoft Office? Not to worry, you can catch it on-demand at your leisure. I’ve attached the slides as well.
The session covers how to:
All directly from Microsoft Office tools, including Word, Excel, PowerPoint and Outlook.
Here’s a transcript of the Q&A segment held at the end of the session for ease of reference.
Is there a SAS Add-In for Microsoft/Access?
The SAS Add-In is invoked via Excel, Word, PowerPoint, SharePoint and Outlook. SAS can read from and write to MS Access via SAS/ACCESS to PC File Formats or ODBC.
We run SAS on a separate server. Is data stored on that server but not defined in the metadata available to the SAS Add-in?
Data used with SAS Add-In for Microsoft Office should be defined in the metadata for full functionality.
Can I use Excel data with the SAS functionalities (tasks)?
Yes. Open your data in Excel and then choose the SAS tab. You can then choose from the available tasks in order to process the Excel data.
Is there a method to add a required FOIA footer when exporting the data into Excel for analytics? Also, can you force a footer to be added when running the report in Excel?
You can set default titles and footnotes. Choose the Tools->Options->Tasks to set default titles and footnotes.
Is there a SAS server component required in order to use the MS Office Add-Ins, such as those demonstrated here?
Yes, a SAS server must be licensed.
In Excel, Manage Content button, the option to "Send To" is greyed out on my PC. Why?
If you are sending to Word or PowerPoint, it must be a report, as these tools are not set up to manipulate data in the same way that Excel is. Please check the type of output you are sending as well as the destination. If you still experience please contact SAS Technical Support.
Can you save the SAS program? Is the program associated (linked?) with the Office document in any way, or does it just create a .sas file?
You can select ‘Export’ in the Code window. This will create a file that can be stored in the location of your choosing.
Do you typically give external users access to the SAS - Add In, since they could edit data using this tool?
SAS Add-In for Microsoft office must be installed for a user to have the SAS tab and access to SAS data for editing within Excel. Even with this step, an administrator must set permissions regarding whether a user has access to edit the data or not.
We currently run PC SAS 9.4. Do we need an additional license for the SAS Add-In for Microsoft Office?
SAS Add-In for Microsoft Office is a separately licensed product, so you would need a license that covers this product.
What happens if you send a document to someone that does not have the Add-In installed?
The recipient will see a static version of the document.
Is this programmable through Visual Basic?
You can use Visual Basic with SAS Add-In for Microsoft Office. Below are a couple of examples:
When the PowerPoint with graphs created via a stored process is saved and then shared with someone who does not have SAS Add-In for Microsoft office, what will they see?
They will see a static version of the graph/report.
Can we add the graphs and tables in a different tab in Excel?
Yes, you will be prompted for the output destination when you specify the data source in the task.
If you use a SAS Program to create content in Excel, can you use the "Refresh" button later to update using the original SAS Program?
How do I share a stored process with others? So far I have only been able to store it in my personal folder in the metadata but no one else can see it.
Please work with your SAS admin to arrange permissions in metadata folders that can be viewed and potentially updated by others.
Can you add 2 SAS data sets into Excel and relate (join) them together or is there another way to do this?
You could do this through the Code window. Often, SAS Enterprise Guide is used for data preparation in these situations.
When we run the SAS code inside Excel, can we see log widow to identify any syntax errors?
Yes, there is a Log tab in the Code window.