Adam, That's correct -- currently there is no user interface (like VIEWTABLE) to allow you to subset the data in place. All of the filtering steps in EG are recorded as steps in the project so that you can re-run them as a flow, and each step must result in another output table. To save space, you can alter your query/filter step to create a VIEW instead of a TABLE. Also, if you want to really modify the data permanently in place, you can create a code step that performs a DATA step to do that work: [pre] data work.class; set work.class(where=(age>14)); run; [/pre] We are looking at ways to make this better in a future relase so that you can apply adhoc filters without creating new tables. Chris ... View more

Andreas, You should track this with technical support. We've seen similar cases and even fixed some in EG 4.1 hotfixes and in EG 4.2. Chris ... View more

Joshua, I think that one of the holdups is an officially supported Java runtime from Sun, since parts of SAS require a JRE. My understanding is that things pretty much work, but we cannot state official support without an officially sanctioned JRE. But I might be speaking out of turn here. Your best bet is to track it with tech support. ... View more

You might need to contact tech support with this one. There are a few SAS coding practices that can cause the current program to seem to hang. For example, if you end your program with an ENDSAS; that would cause a problem. We would need to look at your first program to help diagnose. Chris ... View more

Doc and others, We (in R&D) have completed and signed off on the Vista-aware version of Enterprise Guide. It will have an install that works on Vista, plus all EG updates through the latest hotfix (hotfix 6). There are a few more activities that have to occur in the pipeline before it ships. I believe it is supposed to be available for shipment in early May. Chris ... View more

EG uses the INFOMAPS engine to read Information Maps, and that engine relies on a Java runtime on your server. You can check the basic configuration of the Java runtime with this code: proc javainfo; run; And like Doc suggests, you will probably need to contact tech support to help with the resolution. Chris ... View more

Changing the format in metadata may not be enough. If EG is opening the data using the META engine (which sees things through the filter of metadata), then your format would be applied. However, if this is a preassigned library that EG is reading with the native library engine (ORACLE), then the database attributes of the "live" data are used -- the metadata attributes don't affect it. Chris ... View more

Our SAS Report expert confirms that these differences with the ESCAPECHAR are fixed in SAS 9.2, and render correctly in SAS Enterprise Guide 4.2 (to be released later this year). Chris ... View more

Doc, You might be able to control this somewhat by specifying a different default chart size. By default, ODS determines the "optimum" chart dimensions for the ODS destination that you have open -- RTF in this case. You could exert some control over that by specifying your own dimensions in the Tools->Options->Results->Graph panel, and you might do better in image file size. Chris ... View more

It sounds like you want to have a display name and an actual value for each item in the list. You cannot do this in the query builder with project parameters, but it is supported when you create a stored process. In our next release, this is supported with the new project prompts. Chris ... View more

Just FYI, I think I was the developer at the EG station that you spoke to in San Antonio. So it was me confirming what I had said in this forum, which might detract from the credibility of my comments. But I can see that you took good notes, at least 🙂 Chris ... View more

Darryl, You should contact tech support with this issue. Also make sure you have the latest hotfixes. The issue you are seeing is related to opening/editing a file from a remote server. We've fixed issues like this in hotfixes; if you have the latest hotfix and still experience the problem, then we need a support track to help us investigate. Chris ... View more

Chuck, It's true that .sas7bdat files have different encoding representations depending on the platform architecture. However, SAS on any platform can read a .sas7bdat file from any other platform, using a feature known as Cross-Environment Data Access (CEDA). When using CEDA, there are a few limitations perhaps on performance and ability to update the file in place. However, you can at least read the contents of the data and create a "native" copy with DATA step or PROC SQL, for example. More info at: http://support.sas.com/documentation/cdl/en/lrcon/59522/HTML/default/a002118677.htm Chris ... View more

One big difference: EG 2 does not use the SAS Metadata Server. It uses an EG-specific repository that predates the SAS Metadata Server. If you have a central EG repository, the communication is via Windows DCOM which may not be subject to the same timeout issues. The EG admin guide, linked from http://support.sas.com/eguide, might help if you haven't already dug into it. Chris ... View more

As you have already discerned (I think), there are two connections at work here: EG to metadata and EG to workspace. When a workspace is chugging away processing a job for EG, EG pesters the workspace server every so often (let's say 30 seconds) to ask: "got some SAS log for me? How about now? Okay, how about now?" (This reminds me of my 5-year-old asking to watch television.) But EG never talks back to the metadata server, because we've got all of the metadata we need for the moment, thank you very much. After an hour, your connection takes this inattention personally and hangs up. Now we get to the crux of the problem: EG 4.1 cannot recover from this very well. Eventually EG will need metadata information again -- your session cannot continue without it. But EG is not trained to reestablish this connection in mid-session. This is a limitation that we have fixed in 4.2. We did not add keep-alive logic, but we did add the ability to reconnect to metadata. Unlike a workspace session, the metadata session is stateless and an interruption like this should have no adverse affects, providing EG can successfully reconnect. Hopefully, the information shared in this thread (by everyone) will provide some ideas for workarounds in the meantime. Chris ... View more