The feature that you're looking for, often called "cascading prompts", is not available in EG 4.1. Chris ... View more

The query builder in EG generates SQL that is designed to have a very good chance of passing through to the back end database for processing. It relies on "implicit passthrough", a feature of the SAS/ACCESS database library engines. The implicit passthrough layer optimizes the query for the particular target database, translating the SQL to the dialect that the database would best understand and process. That said, there are a few operations that can prevent efficient processing with implicit passthrough: * use of SAS-specific functions within filter expressions (for example STNAME), because the database has no functional equivalent. * joins of tables where at least one table resides in SAS instead of the database. One remedy: upload the SAS table to the database first. Or if the table is small, simply use the values from the table as literals within the query instead of performing the join. All of this is designed to optimize the result set brought back from the database into your SAS session. When using SQL, the entire content of the table is never brought back all the way to the EG client machine. EG reads only enough records from the table to display them in the data grid (so, about 40 records at a time) Chris ... View more

The limitation is that EG 4.1 doesn't tolerate folders with identical paths among different repositories. Because EG presents this as one aggregate view of everything -- it does not merge folder contents that originate in different repositories. For example: FOUNDATION\BIP Tree\Report Studio\Reports\Stored Processes HR\BIP Tree\Report Studio\Reports\Stored Processes Would create a conflict -- ONLY IF EG is pointed at the HR repository, which "looks through" to Foundation. Chris ... View more

It could be any of a number of issues. Can you run any tasks on it? Or even just run from a code node: proc print data=odsh.person_detail; It's possible that some column values contain national characters (such as found in a native Polish name, for example) that cannot transcode into your SAS session encoding (wlatin1, good for English and Western Europe, usually). Chris ... View more

To update library metadata (changing table definitions and potentially creating new ones), you must have Write Metadata and Create Metadata permissions for the library in question. When you connect to a SAS Metadata server with EG, you are authenticated as one identity that may or may not have these permissions. Because updating metadata is somewhat of an administrative function, you might need to specify credentials for a different identity -- one that has the appropriate privileges. That's what the task offers: a way to specify those credentials without having to re-authenticate as a different identity in your EG session. Chris ... View more

Ravi, Having SAS installed makes a difference. In that case, EG would use SAS to read the local data -- if SAS is registered properly, which perhaps it is not. To make sure, go to a command prompt window. CD to the directory where SAS is installed (ex: "C:\program files\sas institute\sas") and run this command: sas /regserver Then try your test in Enterprise Guide again. Another thing to check: in Enterprise Guide, choose Help->About, then click System Information. That window will tell you what version of SAS that Enterprise Guide thinks is installed and registered on your machine. Chris ... View more

The inttechc bundle is located on the media (CD) that you used to install Enterprise Guide. From the root of the CD path, it's in eguide\bundles\inttechc\setup.exe. Chris ... View more

Yes, that is an important point. SAS/CONNECT and SAS Integration Technologies are two similar, but distinct, products. SAS/CONNECT allows you to connect to data and submit jobs on a remote SAS server from another client SAS session. Note that you have SAS sessions at each end point. SAS Integration Technologies allows you to connect to data and submit jobs on a remote SAS server from any arbitrary client application -- for example SAS Enterprise Guide or even a custom application. In this case, one end point is a SAS session and the other is a client application driving IOM (the object model facilitated by SAS Integration Technologies). It is possible to use these technologies together -- but they each must be licensed and installed at the appropriate end points. Chris ... View more

Are you wanting to simply store the EGP file on one server vs. another? If so, you can do this with File->Save As to save the project to a new location. If you are wanting to do the more complicated task of replacing references in your project from one server to another -- for example "ServerDev" to "ServerProd", you might try the Tools->Replace SAS Server tool. Chris ... View more

When you don't have SAS installed on your local machine (sounds like you don't), then EG uses the SAS OLEDB Local Data Provider to read local SAS data sets. It's possible that there is a problem with that provider on your machine -- either missing or not completely installed. You should probably contact tech support about this issue. Chris ... View more

When you publish a report, you have two choices: publish to a channel or to the report repository. The error you cite indicates that you published to a channel. To share a report with Web Report Studio, you need to publish to the report repository -- an option that is available only if you have configured the report repository web service with Web Report Studio. Chris ... View more

You can publish SAS Report output (srx) from EG to Web Report Studio using the Publish menu. If your SAS Report output was created using one or more stored processes, the results in Web Report Studio will be "refreshable", meaning that you can refresh the report and it will rerun the stored processes for the latest results. This requires that you have the report repository services configured and running with your Web Report Studio setup. This SAS note provides some guidance: http://support.sas.com/techsup/unotes/SN/018/018324.html Chris ... View more

You can submit SAS MPCONNECT code from within EG and, provided that your server has the correct infrastructure, it should work as expected. In this scenario, you are using EG to connect to a single workspace SAS session, and then MPCONNECT is farming out the various jobs to other SAS CONNECT servers that you have configured. If you use EG to run tasks/code on multiple SAS servers that you have configured (ex: SASMain, SASMain2, etc), EG will run tasks in parallel as long as the tasks do not depend on each other's results. In this scenario, EG is simply submitting multiple jobs across the various servers and collecting the results in a single place (your EG project). More information about SAS parallel processing and scalability is available at: http://support.sas.com/rnd/scalability/ Chris ... View more

PROC IMPORT does make use of other SAS language facilities to do its work. So while you issued PROC IMPORT, it's possible that the procedure is using PROC SQL behind the scenes to do some of the work. For example, PROC IMPORT issues DATA step calls to import text files. The difference in column name behavior (SEC/C vs SEC_C) is due to the OPTIONS VALIDVARNAME=ANY that EG submits. If you want your PROC IMPORT step to remap the column name to an acceptable traditional SAS name, put an OPTIONS VALIDVARNAME=V7; statement at the top of your program. Chris ... View more