Data_null gave you the choice.  You can either do 3 PROC REG's and maximize the number of observations for each, or do one PROC REG and have the same number of observations for them all. ... View more

Although you may want to do that, it is generally considered poor form for a graphic.  The numbers on the top distort the visual image (and impact) of the graphic.  Better to put the numbers below or in a separate table.  If you must do it (sometimes the boss insists!), this Google search will provide examples bar chart numbers above site:sas.com ... View more

Try googling forest plot site:sas.com There are lots of examples of forest plots with extra data presented. ... View more

When you open a dataset to look at it in EGuide, there is a default number of records that it reads (I think 1000).  You can change the default under tools --> options. ... View more

You may be able to override it in your code by specifying the font before the GPLOT. ... View more

Hima, Places to look for the Albany AMT font declaration are in earlier in your program, or autoexec.sas, or sasv9.cfg in that order. ... View more

"trash it" is not very well defined.  There are lots of ways to write technically correct code that will cause a database server to have problems.  Chris mentioned one (writing the query so all the data must be passed to the SAS server from the Teradata server).  Another one is to write a JOIN that is a Cartesian product (in database terms a "full outer join").   I don't think that SAS will give any sort of warning on that, as it is a legitimate query in certain situations.  In addition to I/O time, that one can fill up a disk drive in a hurry. Yet another is to do a join using a field that is not indexed.  The database typically has to build the index, do the join, and then delete the index.  It can take a lot of time for big tables.  I'm not sure how Teradata handles that, but it can really slow down an Oracle query.  Sometimes the database can't even build an index and has to slog through multiple tables over and over again to deliver the results (">" or "<" in a join can cause this). SAS provides us with lots of power and EGuide can help by writing technically correct code, but the user still has to think about what he or she is doing. Doc Muhlbaier ... View more

Reddy, You may want to repost this to the Enterprise Guide forum.  A lot of the responses you have gotten refer to writing code rather than the EGuide export task (and it is unclear which you used originally).  Also, you said you are using a PC Files server, but the error message indicates the server is on a Linux box. ... View more

EGuide runs on your workstation.  So your workstation must be turned on and connected to the resources it needs to run a task.  When you schedule the task in EGuide, you can also tell it to run whether or not you are logged in and the workstation status must be consistent with the setting. here are some resources on scheduling in EGuide: Not Just for Scheduling: Doing More with SAS Enterprise Guide Automation - sasCommunity ... View more

Not an error, a feature.  This is a feature of IEEE floating point operations and the fact that some number in base10 cannot be represented identically in base2. SAS stores all numbers a floating point.  base10 and base2 can represent base10 integers identically, but not all base10 decimal numbers.  This reference will tell you more than you want to know about how SAS handles precision SAS(R) 9.4 Language Reference: Concepts, Fourth Edition ... View more