04-17-2012 01:21 PM
Yes, unfortunately this was a casualty of having a 64-bit version of EG. In the 64-bit version, EG cannot contain the 32-bit version of MS Word, so that was going to be problematic.
Even in the 32-bit version (where it could possibly still work), the decision was made to change the behavior. Embedding Microsoft Word in another application has always been tricky and difficult to maintain, as various updates to Office and the operating system can cause it to stop working properly. There is built-in RTF component that could be used instead (basically with the same capabilities as WordPad), but that viewer is not "rich" enough to render all of the content that SAS can produce (especially when it comes to charting).
I encourage you to share this feedback with SAS Tech Support as a suggestion. If the R&D team receives the message that this is an important feature, perhaps they will continue to investigate alternatives.
04-17-2012 02:29 PM
It's not a show-stopper, but an inconvenience. Especially, as an academic organization, our Microsoft Office Add-In does NOT include Word, which significantly inhibits our use of the SAS Report for output (since it can't export to Word without the Add-In).
04-17-2012 02:39 PM
It's not an automatic process, but you can copy/paste SAS Report content into Word and it should do a pretty good job of maintaining the formatting. "Copy" puts an HTML version of the content on the Windows clipboard, and Word readily accepts HTML pasted in.
The Add-In is needed to "Send To" Word because that feature relies on the Add-In to interpret SAS Report from within the Word session.
04-18-2012 11:12 PM
On the plus side, you can 'imbed' a .docx word document now in a project, without EG trying to import it as a datafile.
I reckon it would be nice if SAS could include the Add-in for Word now with SAS EG as compensation for taking out the RTF viewer!
05-24-2012 01:48 PM
That's actually a very good observation. Viewing these document types inside EG will cause EG to load components of WinWord, IE, and Acrobat Reader (respectively) into the EG process space. These are synchronous operations (you must wait while the document is opened and can't interact with EG) and the components plus the document content are loaded into the EG process memory space.
It's convenient, and for small-to-medium results it doesn't affect your experience. But if you want to optimize and don't mind the external windows, this is something to try.
For very large results, EG will automatically open an external viewer. This is meant to protect the EG process from an out-of-memory condition, which could otherwise cause you to lose work.