hi   The Chart Object can draw its own plot. The Image Viwer object can be used to display an existing image.   You can get the help for these object while developing your application. See screenshot below.   So depending on your needs: to display an existing image, use the Image Viewer control. to display a GRSEG catalog entry, use Graph Output control. the Chart (Histogram, Scatter, ...) control will create a graph on the fly and allows you to change the X and Y axis varables dynamically.   So have a look at the doc for the corresponding Control to see what can be done with it.     You can find more resources on doc and getting started with SAS/AFG here http://support.sas.com/software/products/af/index.html#s1=2   Bruno ... View more

Hi   The _ERROR_ is an automatic variable within the DATA Step. You do not have the same variable available in DS2.   From the doc: Automatic Variables _ERROR_ is 0 by default but is set to 1 whenever an error is encountered, such as an input data error, a conversion error, or a math error, as in division by 0 or a floating point overflow.   I assume there is some data type conversion, this triggered the _ERROR_ to be set to 1, whereas this does not happen in DS2.   Bruno ... View more

Hi   the LAG function has to be executed for every row.   Find below the changed code. The LAG function is executed for every row, if we are on the first row of a group we reset the value for the variable x.   data t; input cust_id date:date9. sales; format date date9.; cards; 001 23feb2017 100 001 22jan2016 200 001 23mar2017 300 002 01jun2015 200 002 03aug2016 300 002 05apr2016 400 ; data t1; set t; by cust_id; x =lag(date); if first.cust_id=1 then do; x = .; end; format x date9.; run; Bruno ... View more

hi   Arguments for SAS macro functions are separated with a comma, your scan expression should look like this: %scan(&retailers, &i) Bruno ... View more

Hi   I agree with @RW9 I would no longer develop SCL based applications.   Here is a brief guide on how to use OLE objects within your frame entry, provided you run SAS on windows. Please note this guide was created in 2002.   How to use the OLE Insert Class The sashelp.classes.insert_c class is basically a dot notation style object of the SAS Version 6 "OLE - Insert Object". You can still use the SAS Version 6 one if you want, but then you won't be able to do simple dot notation with it. The following steps outline how one can use any OLE object within a frame using the sashelp.classes.insert_c class:   Open/Create a new Frame entry Either add the resource sashelp.fsp.experimentalafcomponents.resource, or add the class sashelp.classes.insert_c to your components window Drag the OLE Insert Object class to your frame A pop-up window will open, choose the Create Control radio button and then select the OLE object you want A new object will be created in the frame that will surface the methods and properties of this OLE object. Unfortunately since Windows 2000 the "Microsoft Web Browser" is not available anymore. There have been some discussions on how one can add it, so it will appear on the list. The following steps worked for me: Add OLE Insert Object to a frame When the Insert Object dialog comes up Select Create Control Use Add Control button Choose c:\winnt\system32\mshtml.dll .   A test on my system that I can not find the above mentioned module, there are plenty of other for Excel, RTF or PDF etc.   Maybe this will help you.   Bruno ... View more

hi   Add the ODS TRACE ON; and ODS TRACE OFF; statements to see which output objects are created.   Bruno ... View more

Hi   In your code the name of the output table is the same as the name of the input table in Proc SQL. Because of this you get the warning: WARNING: This CREATE TABLE statement recursively references the target table. A          consequence of this is a possible data integrity problem.   Considering the ODS OUTPUT statement, check whether the Proc actually creates the output object you are looking for, you can use the ODS TRACE ON/OFF statement to check this, see example below: ods trace on; ods output moments=xmoments; proc univariate data=sashelp.class; var age; run; ods trace off; Bruno   ... View more

Hi   How about using the UUIDGEN() function. This will ensure, that you lways get a unique id.   Bruno ... View more

Hi   First I would change the colors of the two measures errorBarMin and errorBars so that you can distinguish them from each other, currently they have the same color.   Second I would display the new data items within a list table to see whether the calculated numbers are correct.   Bruno ... View more

Hi   To run the same code for all the data values of a variable checkout this excellent blog Implement BY processing for your entire SAS program/ by @ChrisHemedinger   I think the processing for each make can be improved, by just using the Proc SQL at the end with the additional where clause added.   Please also note, that SAS data set names may not contain any blanks, so you have to remove the blanks from make with for instance the COMPRESS function.   Bruno ... View more