08-05-2011 01:35 PM
I think you have to better explain what you are trying to do. You can always merge two or more datasets using either a datastep or proc sql and then export the file to Excel.
08-05-2011 02:05 PM
Here's some additional detail:
I've just set up SAS-EBI 9.3 and installed MS Add-In for Excel 4.3 on a client to test. I am exploring the functionality of the SAS tab within Excel and would like to create a filter that accesses variables from more than one SAS dataset in a SAS library.
08-07-2011 12:36 PM
This sounds like a job for either an information map or a stored process.
In the information map, you can define the relationship between the tables (one to many, one to one, etc) and the type of join. Then, the information map can be accessed by any of the client applications that support information map access. The end user will only see the "final" results and will not have to worry about the fact that what they see is the result of a join/merge process.
Another alternative is to code you join in a stored process and return the stored process results to Excel using the SAS Add-in. The method you use will depend on what you feel comfortable with and whether you are comfortable with Information Map Studio and/or the coding needed to create a stored process.
08-08-2011 03:41 PM
Thank you Cynthia.
I appreciate that there are various ways to create data for use in Excel. However, in this situation I would like end users to be able to access various existing datasets via the SAS Add-in for Excel, then create a filter to refine the results.
08-10-2011 04:35 AM
The two most common ways for end users to combine tables in SAS is (as Cynthia mentioned) is Information Maps (to have a power user define them for you, or if you are competent enough, do it your self), and Enterprise Guide. There is no currently available functionality in AMO to combine tables
If your users are competent enough to combine tables, I think that Enterprise Guide could be suitable tool for them.