I think your problem is Enterprise Guide had deprecated the use of DDE. Here is a exert from a Chris Hemedinger paper (2008) [http://www.nesug.org/proceedings/nesug08/ff/ff16.pdf] DDE IS DOA DDE, or Dynamic Data Exchange, is a 20-year-old protocol that Microsoft Windows applications can use to send messages and commands to each other. The SAS programming language includes a FILENAME statement access method for DDE to facilitate conversations between SAS for Microsoft Windows and other applications. For years, SAS programmers have used DDE to read and write data programmatically in Microsoft Excel worksheets. When the SAS program runs, it issues commands to start a Microsoft Excel process and establish a communication link, open workbook files, and access data in particular worksheet cells. It's interesting to watch such programs in action because Microsoft Excel windows pop up and values appear in cells as if they were typed in by an invisible hand. DDE technology works only under certain conditions, and these conditions are often not met when using SAS Enterprise Guide. One condition is two processes that are communicating via DDE must be running on the same machine. In a distributed environment where SAS is running on a remote server, the version of Microsoft Excel on your local PC is inaccessible to your SAS program. Remember, the DDE link is between Microsoft Excel and SAS, not SAS Enterprise Guide. The remote SAS session might even be running on a system other than Windows, such as UNIX, where DDE isn't supported at all. The second requirement is that the SAS session must run in a windowing environment. Even if your SAS session is running on a PC that has Microsoft Excel installed, the SAS session is running headless, which means that it has no visible windows. Without this window environment in place, DDE (which relies on Windows messages) is not effective. SAS Enterprise Guide has built-in features to import and export data to and from Microsoft Excel, and you can use those features to gain back some of the ground lost without DDE. However, SAS Enterprise Guide doesn't offer the same level of control at the cell level as DDE. And a KB note to confirm .... 20767 - Use of DDE in SAS® Enterprise Guide® or SAS\CONNECT® software is not supported Without digging into the EG settings I think even x commands are out so writing a script that would take the resulting sas file and apply the password is out. You might want to post under EG as well to see if someone has a work around. I am out of ideas. Sorry EJ ... View more

Ok I got it now.  I think   has a good solution .  Alternatively adjusting the end of the code I had to the following could help as well: data have2;   set have (in=a) forbin(in = b keep=binstart rename=(binstart=value));   if a then weight = 1;   if b then weight = 0; run; proc format library=work cntlin=forbin (rename=(binstart=start binend=end)); run; proc freq data=have2;   format value bin.;   table value ;   weight weight / zeros; run; Good luck! EJ ... View more