Resolving Differences Between Client and Server Graphs | SAS.GRAPH 9.1 Reference, Volumes I and II

A client graph is rendered on the client s (recipient s) system using data sent from the server. The user may be able to manipulate and interact with the graph. Client graphs are intended for display on the Web. Graphs generated with the JAVA and ACTIVEX device drivers, for example, are client graphs.

A server graph is rendered on the server (the machine where the SAS session is running). Interaction with server graphs is limited to features defined by the server such as drill-down links and pop-up data tips. A server graph may or may not be intended for display on the web. Graphs generated with the GIF, JPEG, and PNG device drivers, for example, are server graphs.

Because of technological differences between SAS, Java, and ActiveX, client graphs may differ from server graphs even if the graphs are generated with the same SAS procedure code. In addition, graphs generated with Java may differ from graphs generated with ActiveX. The graphs may differ in appearance, in the default values used for certain options, or in the availability of certain features.

For example, differences between client and server graphs may occur if you are using a global statement or procedure option that is not enabled for that applet or control. Most global statement and procedure options are fully supported by the client device drivers. Exceptions are identified in the procedure and statement documentation and summarized in Appendix 1, Summary of ActiveX and Java Support, on page 1507.

In certain cases, differences between client and server graphs can occur when an applet or control overrides the default value of a procedure option. To resolve this issue, specify a value for the option rather than relying on the default. For example, consider a bubble plot that is being displayed in the Graph applet. The default bubble size is 5. The Graph applet overrides that default with a larger bubble size. To apply a bubble size of 5, specify BSIZE=5 in the BUBBLE statement, rather than relying on the default value of the BSIZE= option.