Or perhaps you want the mean and standard deviation in each row? data all;                                                                                                                                                                           set crossoverdesign;                                                                                                                                                             SBPmean = mean(Sysd1r1, Sysd1r2, Sysd1r3, Sysd2r1, Sysd2r2, Sysd2r3, Sysd3r1, Sysd3r2, Sysd3r3);                                                                                 a           DBPmean = mean (Diasd1r1, Diasd1r2, Diasd1r3, Diasd2r1, Diasd2r2, Diasd2r3, Diasd3r1, Diasd3r2, Diasd3r3);              SBPsdt = std(Sysd1r1, Sysd1r2, Sysd1r3, Sysd2r1, Sysd2r2, Sysd2r3, Sysd3r1, Sysd3r2, Sysd3r3);                                                                                 a           DBPstd = std (Diasd1r1, Diasd1r2, Diasd1r3, Diasd2r1, Diasd2r2, Diasd2r3, Diasd3r1, Diasd3r2, Diasd3r3);                                                                                run;   Richard ... View more

Means and standard deviations of the variables SBP DBP will be meaningless because even if converted back to numbers the resulting values will be beyond the range of numeric precision for SAS (15/16 digits in Windows and Unix).  I suspect then you need to analyse each component individually. Proc means mean std data = all ;      var Sysd: Diasd: ; run ; Richard ... View more

You do not specify what statistics you want so I suspect Proc Freq (counts and percentages) might be what you require. Proc Freq data = all ;      Tables SBP DBP SBP*DBP / List ; Run ; Richard ... View more

You have (by default) defined SBP and DPB to be character variables in constructing table all.  The concatenation operator (||) implies a charactr process, and SAS automatically converts numeric data to character in such a case. Summary/Means is intended only for numeric variables. Richard ... View more

SAS supplies a tool - LSF - to cover situations like this. If you are restricted to base SAS and can use a server (eg windows server) scheduler you need to write a short control program that will run at specified intervals and test for the existence of your file drops - fileexist() - hopefully your applications delete the previous files once they have been processed.  Then when all present and correct your control program can %include the flows and perhaps set a flag in a persistent text file showing you are all done for the day and preventing further runs of the flows. Richard. ... View more

I think Proc SQL is expecting aliases to be declared proc sql;      select *      from ball04 b4 intersect all      select *      from ball06 b6      where b4.player=b6.player; quit; Richard ... View more

How you do this depends on where your SAS executables are located.  If they are on a local machine that your customer has access to you can make a copy of the SAS icon and add the parameter -sysin='your_program_here.sas' to the startup script.  Alternately your button could use the amended script to launch the program in batch mode.  You would also need to redirect the log so any problems with the input data could be identified. If your SAS resides an a server and typically you access it using Enterprise Guide then I would suggest creating a project containing a process flow that would analyse and output the customer data. f you need more help you will have to describe your setup. Richard ... View more